Skip to main content
Glama
Sign In
tas-guard

tas-guard

by intoApex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get_stock_latest_quote

Read-only

Fetch a simulated current quote for a stock symbol to preview demo prices before placing orders through guarded workflows.

Instructions

Simulated latest quote for a symbol (demo prices).

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": {
      "symbol": "<symbol>"
    },
    "name": "get_stock_latest_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.3

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: the quote is 'simulated' with 'demo prices', warning the agent that the data is not real market data. It stops short of describing latency, refresh cadence, or error behavior.

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?

A single short sentence that is front-loaded with the verb and resource, with the key caveat in parentheses. Nothing is wasted, though the parenthetical is slightly awkwardly placed relative to the main claim.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter read-only tool, the description is adequate to call the tool correctly, and annotations cover the safety profile. It omits any hint of the returned fields or symbol format, which would help an agent validate its call.

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 0% and there is one required parameter, so the description carries the burden. It only restates that a 'symbol' is required and adds no format, casing, or validity guidance (e.g., ticker format). Since the parameter name is self-explanatory, this is minimally adequate rather than helpful.

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?

The description gives a specific verb and resource ('latest quote for a symbol') and adds a meaningful qualifier that it is simulated/demo data, which separates it from any real-market sibling. It does not explicitly distinguish itself from the surrounding trading siblings (get_orders, place_stock_order), but the resource is unambiguous.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent must infer usage purely from the name and the parenthetical about demo prices.

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

Deploy Server

Other Tools