Skip to main content
Glama
Sign In

Gaduin

by com.gaduin
OverviewDiscussionsAdmin

Get a market

get_market
Read-onlyIdempotent

One market by id or slug: its question, the rule it settles on, route, outcomes with current prices, volume, close time, status and, once settled, the outcome it settled on, with a link to its page.

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": {
      "id": "<id>"
    },
    "name": "get_market"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesMarket UUID, or the slug from a gaduin.com/markets/<slug> link.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"Market UUID."New value: +"Market UUID, or the slug from a gaduin.com/markets/<slug> link."
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral detail beyond them: the payload is a full market record, and the settlement outcome appears conditionally ("once settled"), which tells the agent the response shape varies by market state.

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

Conciseness4/5

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

One sentence, front-loaded with the lookup verb and scope before the field enumeration. The field list is long but each item is informative about the return payload, which has no output schema to document it.

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?

With no output schema, the description carries the burden of describing the return payload and does so thoroughly, including the conditional settled outcome. It stops short of stating not-found/error behavior or price units, which are the only meaningful gaps for a single-lookup read tool.

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 coverage is 100% and the single parameter already documents both accepted forms, including the gaduin.com/markets/<slug> link origin. The description restates "by id or slug" without adding format, casing, or error semantics, so the schema does the heavy lifting.

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?

"One market by id or slug" names the resource and the singular scope, and the rest of the sentence enumerates exactly what comes back (question, rule, route, outcomes with prices, volume, close time, status, settlement outcome, page link). It separates itself from list_markets by the singular lookup, though it never names a sibling explicitly.

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?

Usage is only implied: the id/slug lookup signal tells an agent this is the detail-view call once a market identifier is known. There is no explicit statement about when to prefer it over list_markets or get_market_price_history, or what to do if the identifier is unknown.

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

All Gaduin toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources