Vericto account (OAuth)

Configuration approval status

config_approval_status

Read-onlyIdempotent

The outcome of a configuration change that apply_config_change sent for approval (connection keys only): pending, applied (with the ids of what changed), rejected, expired or failed. Read-only. Check it when the person says they decided, not in a loop.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "approval_id": "<approval_id>"
    },
    "name": "config_approval_status"
  }
}

Input Schema

Name	Required	Description	Default
`approval_id`	Yes	The approval_id apply_config_change returned.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and idempotentHint, and the description's 'Read-only' merely restates that. The real value added is beyond the annotations: the full outcome vocabulary, the fact that 'applied' returns ids of what changed, the connection-keys-only scope, and the anti-polling warning.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what is returned, followed by safety state and usage constraint. Every clause carries information; nothing is filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the burden of explaining return values, and it does so by enumerating all five statuses and noting the extra ids payload for 'applied'. For a one-parameter, read-only status tool this is complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single parameter is documented as 'the approval_id apply_config_change returned', so the description can only reinforce provenance rather than add new meaning. Baseline 3 is appropriate here since the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (the outcome of a configuration change submitted via apply_config_change) and enumerates the possible results: pending, applied with changed ids, rejected, expired, failed. It also scopes the tool to connection keys only, which separates it from get_config and the other config siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use ('when the person says they decided') and an explicit when-not ('not in a loop'), which is the key failure mode for a status-polling tool. It does not name a sibling for the case where no approval_id exists yet, so routing guidance is not fully closed.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Vericto account (OAuth) tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?