Skip to main content
Glama

reverse-engineer-anything_supermarioworld

fetch_docs

Fetch entire documentation file from GitHub repository: ethanhunt1981/reverse-engineer-anything_supermarioworld. Useful for general questions. Always call this tool first if asked about ethanhunt1981/reverse-engineer-anything_supermarioworld.

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": "fetch_docs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that it retrieves an entire documentation file from a fixed GitHub repo and that it should be called first, but it omits authentication needs, rate limits, response size/format, and failure behavior.

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 the core action and repo scope. Every sentence adds useful guidance with no repetition or filler.

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

Completeness4/5

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

For a low-complexity zero-parameter tool with no annotations or output schema, the description covers what it does, when to use it, and call priority. It could be slightly more complete by identifying which documentation file is fetched or what the return looks like, but it is sufficient to invoke the tool correctly.

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

Parameters4/5

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

The tool has zero parameters, so parameter semantics baseline is 4. There are no inputs for the description to clarify or compensate for.

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?

The description states a specific verb and resource: 'Fetch entire documentation file from GitHub repository: ethanhunt1981/reverse-engineer-anything_supermarioworld.' It distinguishes itself from fetch_generic_url_content by being repository-scoped and from search_docs by fetching the entire file, though it does not explicitly name those 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?

It gives clear conditional guidance: 'Useful for general questions' and 'Always call this tool first if asked about ethanhunt1981/reverse-engineer-anything_supermarioworld.' However, it does not name alternatives like search_docs or state when not to use it.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources