Skip to main content
Glama

reverse

Read-onlyIdempotent

Reverse-engineer what the trader POSTED before saying anything about it: a rule in words, a pasted Pine script (read statically, never run) or a chat transcript. Returns a dossier: the route (what it is and the first tool), findings each marked observation, inference or unknown with an id (E1, E2) and what would settle each unknown, the checklist (market, bar size, trigger, direction, stop, target, stand aside, numbers match the tape, run over recorded bars) as answered, partial or unresolved, and the ceiling (hypothesis until rehearsed). A Pine script is also imported by the runner's importer (import: the cubicle.script, or each refused construct with its code, Pine line and why, and the next step). Cite the ids; never present an inference or an unknown as a fact. For an attached chart use the image tool first.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "text": "<text>"
    },
    "name": "reverse"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYeswhat the trader posted, verbatim: the rule, the Pine source or the transcript

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful behavior beyond that: Pine is read statically and never executed, the dossier's structure (route, findings with E-ids, checklist, ceiling), and the importer's refusal reporting. It stops short of describing size limits or how partial checklists are surfaced, so it is good but not exhaustive.

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

Conciseness3/5

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

Front-loaded with the core action, and every clause carries information, but it is delivered as one sprawling sentence with stacked parentheticals that make it hard to scan. The return-value detail could be broken into a short list rather than embedded mid-sentence.

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?

No output schema exists, so the description carries the full burden of explaining returns, and it does: route, findings with ids and resolution criteria, checklist states, ceiling, and importer outcomes. For a single-parameter read-only tool this is complete enough to call 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?

Only one parameter with 100% schema coverage, so the baseline is 3. The description earns an extra point by clarifying what the single string may contain (a rule in words, Pine source, or a transcript) and reinforcing that it must be verbatim, which helps an agent decide what to paste.

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?

States a specific verb and resource ('Reverse-engineer what the trader POSTED') and enumerates the accepted inputs (rule in words, pasted Pine script, chat transcript). It also names the return artifact (a dossier) and routes chart cases to the image sibling, so an agent can distinguish it from siblings without opening the schema.

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 an explicit alternative for one case ('For an attached chart use the image tool first') and an operating constraint ('Cite the ids; never present an inference or an unknown as a fact'). It does not spell out when NOT to use it for, say, a plain question about a rule, but the trigger condition is clear enough.

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