Skip to main content
Glama
Sign In
Riza MCP Server

Riza MCP Server

by ampcome-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

fetch_tool

Retrieve a tool's source code and configuration by providing its unique tool ID. Use this to inspect or reuse any existing tool's implementation.

Instructions

Fetch a tool, including its source code.

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_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
tool_idNoThe ID of the tool to fetch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.3

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. 'Fetch ... including its source code' implies a read-only retrieval and hints at return content, but it does not disclose failure behavior, permissions, whether source code is truncated, or any side effects.

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?

The description is a single concise sentence with no filler. The core action and key differentiator ('including its source code') are immediately visible.

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

Completeness3/5

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

This is adequate for a simple single-parameter fetch operation, but with no output schema and no annotations it could usefully mention return format, not-found behavior, or the relationship to list_tools for obtaining a valid tool_id. The absence of requiredness information for tool_id is also left ambiguous.

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?

The only parameter, tool_id, is already fully described in the schema ('The ID of the tool to fetch'), and schema description coverage is 100%. The description adds no additional parameter meaning, such as how to obtain the ID or whether it is required.

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?

The description uses a specific verb ('Fetch') and resource ('a tool'), and the added phrase 'including its source code' clarifies what makes this different from list_tools or execute_tool. An agent can tell this is a retrieval operation for a single tool's definition.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus list_tools, execute_tool, or edit_tool. It does not state that fetch_tool is for reading a single tool's details/source before modifying or executing it, nor does it mention any exclusions or prerequisites.

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

Deploy Server

Other Tools