Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Research log

usage_research_log
Read-onlyIdempotent

Every paid lookup and scheduled check in this billing period: who ran it, from where (app, API or agent), and what it cost, with totals per tool. Lookups still running show status running and the amount held for them.

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": {
      "siteId": "<siteId>"
    },
    "name": "usage_research_log"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
siteIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is settled. The description does add real behavioral detail beyond them: rows for in-flight lookups carry status 'running' plus the amount held, and results are aggregated with totals per tool. It stops short of describing ordering, pagination, or result-size 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 dense sentence that front-loads scope and then enumerates returned fields, with zero filler. Slightly long but every clause carries information about the result shape.

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?

With no output schema, the description usefully sketches the record contents, including the running/hold case, which is genuinely hard to infer otherwise. But for a two-parameter reporting tool it omits parameter meaning and pagination, so an agent knows what it will see but not how to scope the call.

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%, so the description carries the full burden, yet it says nothing about the two parameters. siteId is required and undocumented, and limit (default 100, max 500) is neither explained nor connected to any pagination or truncation behavior.

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 states a specific resource and scope: 'every paid lookup and scheduled check in this billing period,' and enumerates the fields returned (who ran it, source, cost, per-tool totals). It does not, however, distinguish itself from billing-usage siblings such as usage_get, usage_events_by_day, or workspace_usage, so an agent must guess which reporting tool to pick.

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 guidance, no stated prerequisites or exclusions, and no named alternative. The only contextual cue is the implied 'billing period' framing, which hints at usage/audit reporting but leaves the choice against sibling usage tools entirely to inference.

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