YourAITools MCP Hub

ToolFit: Audit an agent tool list

audit_tools

Read-onlyIdempotent

Check the tool definitions an agent loads, before they cost tokens or fail: estimated tokens per tool, schema errors per provider (OpenAI, Anthropic, Gemini, Bedrock, MCP; add openai_strict for strict mode) with JSON paths and fixed definitions, tool pairs models will confuse with fix hints, basic poisoning patterns, a grade and a pin (set_id) for diff_tools. Pass "tools" (array in any common format) or "url" (public remote MCP server; tools are listed, never called). level "lite" returns the summary only. Free: 20 calls/day per IP (shared with diff_tools), then $0.003 lite / $0.01 full via x402 or credits.

[ToolFit via YourAITools MCP Hub] Free tier: same as ToolFit's own MCP server (call without payment and without tier). Paid: full $0.01 / lite $0.003 per call, with a credits key (Authorization: Bearer yatc_...) or x402 (USDC; the hub returns the payment terms). Failed tool calls aren't charged: credits are refunded automatically and x402 payments only settle on success.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "audit_tools"
  }
}

Input Schema

Name	Required	Description
`url`	No	Public remote MCP server URL (Streamable HTTP, https), e.g. https://api.youraitools.co/mcp/hub. ToolFit only lists its tools.
`tier`	No	Paid tier: full $0.01, lite $0.003. Omit tier (with no credits key or x402 payment) to use the free tier.
`level`	No	lite = summary only; full (default) = every issue, fixed definitions, pair hints
`tools`	No	Tool definitions: MCP tools/list entries, OpenAI {type:"function",function:{...}}, Anthropic {name,description,input_schema}, Gemini functionDeclarations or Bedrock toolSpec. Max 500.
`providers`	No	Providers to check (default openai, anthropic, gemini, bedrock, mcp; add openai_strict for Structured Outputs strict mode). GET: comma list.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 30, 2026
- addedInput schema / properties / level / examples
```
Added value: +[
+  "lite"
+]
```
- addedInput schema / properties / url / examples
```
Added value: +[
+  "https://api.youraitools.co/mcp/hub"
+]
```
Changed2 schema fields changedOct 24, 2026
- removedInput schema / properties / tools / items / additionalProperties
```
Removed value: -true
```
- removedInput schema / properties / tools / items / properties / inputSchema / additionalProperties
```
Removed value: -true
```
AddedOct 24, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: remote URL servers are listed but never called (a meaningful side-effect guarantee), tools array caps at 500, level 'lite' truncates output, and the free tier is 20 calls/day per IP shared with diff_tools. It also discloses billing mechanics and that failed calls are refunded / x402 only settles on success — exactly the operational facts an agent needs before deciding to spend a paid call.

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

Conciseness4/5

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

The capability and input-mode sentence is aggressively front-loaded and dense in a useful way. However the pricing is stated twice — once in the main sentence and again in the bracketed hub paragraph (free tier, $0.003 lite / $0.01 full) — so a chunk of the text is redundant boilerplate rather than new information.

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?

For a zero-required-parameter, fully documented-schema tool with no output schema, the description still covers what comes back (grade, set_id, per-provider errors, fixed definitions, pair hints), the lite truncation, and the cost/rate-limit envelope. Nothing an agent needs to invoke it correctly is missing.

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%, so the schema already documents tools, url, tier, level and providers, including the openai_strict enum value. The description restates the provider list and lite/full behaviour but does not resolve the genuinely confusing overlap between 'tier' (paid vs free) and 'level' (summary vs full), which is the one place prose could have added real value. Baseline 3.

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

Purpose4/5

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

Names a concrete verb and resource (audit an agent's tool definitions) and enumerates the deliverable outputs: token estimates, per-provider schema errors with JSON paths and fixed definitions, confusable tool pairs, poisoning patterns, a grade and a set_id. That is far more specific than a restatement of the title. It stops short of 5 because it never distinguishes itself from near-neighbours in the sibling list such as scan_tools or check_mcp_server.

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 a clear trigger ('before they cost tokens or fail') and tells the agent which input mode to pick: pass 'tools' as an array in any common format, or 'url' for a public remote MCP server. It also writes to diff_tools via set_id. There are no explicit exclusions or guidance on when scan_tools/check_mcp_server would be the better choice instead.

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

All YourAITools MCP Hub 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?