Skip to main content
Glama

YRUZ how to call a tool (instructions)

get_example
Read-onlyIdempotent

Instructions for any paid YRUZ tool: its parameters (required and optional), a valid call, the exact price rule, the payment steps and the response shape (field names and types). No answer data. Pass the tool name (e.g. deps_check_advisories, promo_create_listing); without it, lists every paid tool with its price.

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

Input Schema

NameRequiredDescriptionDefault
toolNotool name from tools/list, e.g. web_extract

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and no destructive behavior. The description adds useful context beyond annotations: it clarifies 'No answer data' (so the agent knows it's not for retrieving actual results) and describes the fallback behavior when the optional parameter is omitted.

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 front-loaded with the tool's purpose, then adds the key exclusion ('No answer data'), and finishes with usage instructions. Every sentence is necessary and there is no redundancy.

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 meta-tool with one optional parameter, no output schema, and the given annotations, the description is complete: it explains what the tool does, what it returns (instructions including response shape), what it does not return (no answer data), and how to use the parameter (including the no-parameter case).

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?

Schema coverage is 100%, but the description adds value by providing multiple concrete examples (deps_check_advisories, promo_create_listing) and explaining that omitting the parameter lists all paid tools with prices. This goes beyond the schema's single example and clarifies the optional nature.

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 clearly states the tool returns instructions for any paid YRUZ tool (parameters, valid call, price rule, payment steps, response shape), and explicitly contrasts it with actual data by saying 'No answer data.' This distinguishes it from all sibling tools, which are the actual paid tools.

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 indicates usage via 'Pass the tool name' and explains behavior without the parameter ('lists every paid tool with its price'), and clearly excludes answer data. However, it does not explicitly name the alternative (using the actual paid tool for data) or state when to use this versus directly calling a paid tool, leaving some inference.

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.