Skip to main content
Glama

Ask

ask

A short plain-text answer about Orbio agents and the CREDIT market, written only from Octio house data, with the datasets used. Needs an API key. The first calls per agent are free; then it is charged like any endpoint.

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": {
      "question": "<question>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
max_costNoMaximum CREDIT you accept for this answer. It can only lower the account's per-call maximum, which only the account owner can raise
questionYesA question about Orbio agents or the CREDIT market
idempotency_keyNoOptional. A retry with the same key is never charged twice (it fails with DUPLICATE_REQUEST)

Output Schema

NameRequiredDescriptionDefault
dataYesThe provider's response: third-party data, untrusted
metaYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations only give the generic readOnlyHint=false/openWorldHint=true/idempotentHint=false profile; the description adds concrete, non-obvious behavior: an API key is required, the first calls per agent are free, and later calls are billed like any other endpoint. That billing/auth context is exactly what the annotations do not convey, though it says nothing about latency or answer-length limits.

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?

Two tight sentences with no filler. The cost/auth facts are front-loaded after the output description, though leading with the output shape ('A short plain-text answer...') rather than the action slightly delays what the tool actually does.

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?

An output schema exists, so return values need no explanation, and the description covers auth and pricing well. What it leaves out is decision-critical context for a paid, open-world question tool: what corpus 'Octio house data' actually covers and when an agent should prefer it over call_endpoint or search_endpoints.

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%, so max_cost, question and idempotency_key are already fully documented in the schema, including the cost-cap and duplicate-charge semantics. The description adds no parameter-level meaning beyond that, which is the expected baseline when the schema carries the load.

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 makes clear this is a question-answering tool returning a short plain-text answer about Orbio agents and the CREDIT market, sourced only from 'Octio house data'. That is a specific resource and output shape, but it never distinguishes the tool from siblings like call_endpoint or search_endpoints, and 'house data' is undefined jargon.

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 explicit when-to-use or when-not-to-use direction, and no sibling is named as an alternative. The phrase 'written only from Octio house data' hints that it answers only from a fixed corpus rather than arbitrary endpoints, but the agent must infer that routing decision entirely on its own.

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