MCP tools

Grace's tools let your AI agent consult the right instructions, then check its work. You explain what you want to do; it uses the tools it needs.

MCP is how your AI agent connects to Grace. If the connection is not ready yet, follow Connect a project.

The tools

When are they needed?	What the AI agent can do
Before starting a task	Consult instructions from the talents it chose for that task.
An instruction needs explaining	Read that instruction in more detail.
The work is ready for review	Get the verification rules, then apply them to its changes.
An architecture decision needs comparing	Present three distinct options with diagrams, the same criteria, and a recommendation that leaves the decision to you.
Your organization requires a record of the review	Record the results of checking Grace talents and Custom Talents.
You ask to create a lasting organization rule	Help you write a coherent rule, have you approve its exact contents, then save an unpublished draft. This is reserved for owners and admins.
You have approved new talents	Add those talents to the project.
A talent seems incomplete or incompatible	Identify missing prerequisites and conflicts.
You need to choose your first talents	Examine the project and propose talents for your approval.
You want to report a problem or suggest an idea	Prepare feedback limited to useful information, show you exactly what would be sent, then wait for your explicit approval.

Remember: Grace provides the instructions. The AI agent does the work and the review. Obtaining a list of rules does not mean the changes have been checked.

The agent chooses talents relevant to your request, then receives the detailed procedure when it starts the review. This review must focus on your changes. It does not replace project tests, builds, or lint checks after the last fixes. If the agent cannot use an independent reviewer, it must disclose this limitation.

At the end of a Grace-assisted task, the agent's answer ends with a "Grace's contributions" block containing only a table. Each talent that actually contributed has a row, without an arbitrary limit, showing its status, concrete contribution, and observed evidence. The statuses distinguish what was improved or verified from what remains unapplied, unverified, or unresolved. Talents without a contribution are omitted. If no talent contributed, one explicit row states that no contribution was observed.

When grace_prepare_task supplied a URL, the block ends with "View the resolution in Grace". A project member can open it to see the same details as in the drawer: workflow, findings, fixes, and evidence. The agent omits the link if Grace did not provide it, rather than trying to reconstruct it.

Recognize the names shown in your AI agent

Displayed name	What it does
`grace_prepare_task`	Prepare instructions for the task.
`grace_deepen`	Read an instruction in more detail.
`grace_review`	Obtain the review plan and rules.
`grace_record_validation`	Record the review verdicts and evidence.
`grace_present_architecture_comparison`	Present three comparable architecture options and a reasoned recommendation when your profile preference or the project setting enables it.
`grace_create_organization_talent`	After your explicit request and approval, save an organization talent draft without activating it.
`grace_install_talents`	Add talents you approved.
`grace_doctor`	Find missing prerequisites and conflicts.
`grace_discover_codebase`	Help choose the project's first talents.
`grace-feedback`	Start guided preparation of voluntary feedback.
`grace_submit_feedback`	Submit only the contents you just approved.

Compare architectures

Configure this mode in Grace independently of talents. It is enabled by default under Profile > Architecture comparisons, where each user can turn it off. A project can require it for the whole team under Project > Settings > Architecture comparison. The project setting takes precedence; otherwise each member follows their profile preference. When both are off, the tool is not exposed to the AI agent.

Ask your AI agent to compare an architecture decision. After consulting the active talents and project context, it presents exactly three options, each with a diagram, main components, advantages, risks, complexity, operational considerations, and migration. A table applies the same criteria to all three options before the recommendation.

The recommendation explains how the option fits your constraints and the main trade-off. It does not approve the decision on your behalf.

In a client compatible with MCP Apps interfaces, the comparison also appears in a visual view within the conversation. In other clients, the same content is available as Markdown with Mermaid diagrams: the enriched interface is never required for the full comparison.

Send feedback from your agent

The prompt and submission tool are offered only when your agent is connected to your Grace account through OAuth. A project API key cannot discover them or send feedback.

Launch the grace-feedback prompt from your agent's MCP interface. Describe the issue or idea; for an issue, specify the expected result, observed result, and impact.

The agent locally removes secrets and personal information, then shows the exact contents before sending. Check every field: automatic removal may miss sensitive information. An optional PNG or JPEG screenshot is limited to 2 MiB and must be cropped or redacted before approval. Also describe in text any necessary information visible in the image: the screenshot is a visual supplement.

Nothing is sent without your explicit approval. The report goes to Grace platform administrators along with a link to your account, organization, project, and client used. The report and screenshot are deleted after 30 days. If submission fails, the agent keeps the draft in the conversation and can claim success only with an FB-… reference.

Pentest mode tool

Pentest mode uses a separate MCP connection that exposes just one tool:

Displayed name	What it does
`grace_pentest_guidance`	Get versioned instructions for a security test phase. The call accepts only a phase, AI agent, and language from predefined choices.

The general Grace server must be disabled in this session. Testing, subagents, tools, evidence, and the report remain your AI agent's and client environment's responsibility. See Connect a project to enable it.

What you must approve

The AI agent proposes talents to install and waits for your approval before adding them. Project discovery alone does not install talents.

To create an organization talent, it first shows the exact name, instruction, application mode, and triggers. Any change to this set requires your approval again. The tool saves only a draft: publication is a separate action in the Grace dashboard.

If Grace does not respond or denies access, see Troubleshooting. To learn about the proposed expertise, read What is a talent?.