Skip to main content
Glama
Sign In

Nyria

by io.github.Nyria-LLC
OverviewDiscussionsAdmin

Recent orders

nyria_recent_orders
Read-onlyIdempotent

View recent orders placed through your strategy. Shows order_id, instrument, action, status, quantity, price, and timestamp. Pass an order_id to nyria_order_status for its fill.

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

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of orders to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without prose. The description usefully adds the response field set (order_id, instrument, action, status, quantity, price, timestamp) since there is no output schema, but it leaves ordering and the meaning of 'recent' undisclosed.

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?

Three short sentences, no filler, and the purpose and returned fields are front-loaded before the sibling hand-off. Every sentence earns its place.

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 compensates well by listing the fields returned, and annotations cover the safety profile for this read-only, idempotent listing. The main remaining gap is that 'recent' is never quantified, so an agent cannot know the default time horizon.

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% with a single optional 'limit' parameter (default 20, max 100), so the schema already carries the semantics. The description adds nothing about limit or ordering, which is acceptable but not additive, matching the baseline for high-coverage schemas.

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 opens with a specific verb and resource ('View recent orders placed through your strategy') and then enumerates the returned fields, so an agent knows exactly what this returns. It also distinguishes itself from the sibling nyria_order_status by delegating fill lookup there.

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 gives clear routing guidance: use this for the order listing, and pass an order_id to nyria_order_status for fill details. It does not state any when-not-to-use condition or how 'recent' is bounded (time window or count), so the alternative is only partially defined.

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

All Nyria 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