Skip to main content
Glama

How to do something on the site

get_guide
Read-only

Step-by-step instructions, with the exact button names, for one task on iomarkets.ai. Without a task, lists the tasks.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhich task. Leave out to list them all.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / task / enum
      Previous value: -[
      -  "look-around",
      -  "runs",
      -  "verify-receipt",
      -  "audit-trail",
      -  "request",
      -  "review-pack",
      -  "pilot",
      -  "cost",
      -  "own-assistant"
      -]New value: +[
      +  "look-around",
      +  "runs",
      +  "verify-receipt",
      +  "audit-trail",
      +  "request",
      +  "review-pack",
      +  "pilot",
      +  "cost",
      +  "re-runs",
      +  "terminal",
      +  "own-assistant"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuine value beyond them by disclosing the output style (exact button names, step-by-step) and the discovery fallback when no task is supplied.

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?

Two short sentences, front-loaded with the primary behavior and then the fallback mode. No filler or repetition of the title or schema.

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 single-optional-parameter read tool with annotations and no output schema, the description covers what it returns and the no-argument behavior. It could note that instructions are site-specific static content, but nothing essential to correct invocation 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 description coverage is 100% and the enum lists all task values, so the schema carries the semantics. The description's phrase 'one task' confirms single-task scoping but adds little beyond what the enum already conveys.

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?

States a specific verb+resource: returns step-by-step instructions for one task on iomarkets.ai. The dual mode (a task vs no task) is clear, though it doesn't explicitly differentiate itself from siblings like get_overview or explain_term.

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

Usage Guidelines3/5

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

The description implicitly tells the agent this tool is for how-to guidance rather than data lookup, and explains the no-task behavior. It never states when to prefer it over get_overview or explain_term, leaving the alternative selection to 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.

Resources