Skip to main content
Glama

Geoa — Get found in ChatGPT

Fix Queue

geoa_fix_backlog
Read-onlyIdempotent

Your current geoa fix queue: the 5 highest-priority GEO fixes served right now (title, effort, impact, delivery channel) plus how many wait in the backlog and how many are verified done. Every fix is closed by MEASUREMENT, never by claim. Read-only — act on fixes in the geoa dashboard. Requires sign-in to a geoa account.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds real value on top: the sign-in requirement, the exact shape of the result (top 5 plus two aggregate counts), and the important lifecycle rule that a fix is only closed by measurement, not by claim. It stops short of noting freshness/caching or what happens when the queue is empty.

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, front-loaded with what is returned, then the measurement rule and the auth constraint. No filler; the emphasized MEASUREMENT clause conveys a behavioral guarantee rather than marketing.

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 correctly carries the burden of describing return contents: the fix fields, the backlog count and the verified-done count. Auth needs are stated. The one missing piece is how this differs from geoa_pending_fixes, which matters given the overlapping-looking sibling.

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

Parameters4/5

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

The tool takes no parameters, so there is nothing for the description to disambiguate and the schema is complete by construction. Baseline applies with no gap to compensate for.

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?

Names a specific resource (the geoa fix queue) and enumerates the payload: 5 highest-priority fixes with title, effort, impact and delivery channel, plus backlog and verified-done counts. Very concrete. It does not distinguish itself from the sibling geoa_pending_fixes, whose name suggests overlapping content, so an agent cannot fully disambiguate from the description alone.

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

Usage Guidelines3/5

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

"Act on fixes in the geoa dashboard" establishes that this tool is a read surface and the actual work happens elsewhere, which is useful routing. But there is no explicit when-to-use or when-not-to-use relative to geoa_pending_fixes or geoa_report_fixes_live — the closest siblings — so usage is only implied.

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