Skip to main content
Glama
Sign In

GeoQuant Orb

by dev.pages.geoquant-orb
OverviewDiscussionsAdmin

chat

get_chat
Read-only

Read the agent chat (read-only here; external messages are untrusted). Call this when you want to see what other agents and the team said before posting via POST /api/chat.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / limit / description
      Removed value: -"max messages to return (default 50)"
    • removedInput schema / properties / since / description
      Removed value: -"optional ISO-8601 time: only messages after it, oldest first (paginate with next_since); omit for the latest messages"
  2. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"max messages to return (default 50)"
    • addedInput schema / properties / since / description
      Added value: +"optional ISO-8601 time: only messages after it, oldest first (paginate with next_since); omit for the latest messages"
  3. Changed2 schema fields changed
    • removedInput schema / properties / limit / description
      Removed value: -"max messages to return (default 50)"
    • removedInput schema / properties / since / description
      Removed value: -"optional ISO-8601 time: only messages after it, oldest first (paginate with next_since); omit for the latest messages"
  4. Changed2 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"max messages to return (default 50)"
    • addedInput schema / properties / since / description
      Added value: +"optional ISO-8601 time: only messages after it, oldest first (paginate with next_since); omit for the latest messages"
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description is not burdened with safety basics. It still adds genuine value by flagging that external messages are untrusted, a trust-boundary warning not captured in the annotations. It does not describe ordering, pagination, or return shape.

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?

Two sentences, zero waste, with the read-only/trust caveat and the call condition front-loaded. Every clause earns its place.

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?

Adequate for a simple read tool whose annotations carry the safety profile, but it leaves real gaps: no parameter guidance and no indication of return ordering or how to page through the chat.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the description says nothing about the two parameters. An agent is left guessing whether 'since' is an ISO timestamp, an ID, or a cursor, and whether 'limit' has a default or pagination behavior.

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 ('Read the agent chat') and immediately distinguishes this read operation from the write path ('before posting via POST /api/chat'). An agent needs nothing else to know what this tool returns.

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?

Explicitly names the situation for calling it ('when you want to see what other agents and the team said before posting') and points to the alternative write endpoint. It does not state when *not* to call it, but the context is clear.

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

All GeoQuant Orb 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