Skip to main content
Glama

Geoa — Get found in ChatGPT

Report Fixes Written and Deployed

geoa_report_fixes_live
Idempotent

Report that you have written the given approved fixes into the site and DEPLOYED them. geoa then fetches the public page as an ordinary visitor and confirms the change is really there — a fix is closed by measurement, never by claim, so a report made before the change is live stays unconfirmed. Writes to the customer's geoa account. Requires sign-in to a geoa account.

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": {
      "fix_ids": "<fix_ids>"
    },
    "name": "geoa_report_fixes_live"
  }
}

Input Schema

NameRequiredDescriptionDefault
commitNoOptional commit SHA or reference the change landed in
fix_idsYesThe fix_ids you wrote in and deployed (from geoa_pending_fixes)
rolled_backNoOptional {fix_id: reason} for changes you reverted instead of keeping
deployed_urlNoOptional URL where the change is now live
tool_versionNoOptional client/tool identifier for the report

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses that the tool writes to the customer's geoa account, requires sign-in, performs an independent public-page fetch to verify, and that premature reports leave fixes unconfirmed. That is real behavioral context an agent needs before invoking a non-readOnly tool.

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, front-loaded with the action and its verification consequence, with zero filler.

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?

Covers the verification loop and account requirements, and no output schema means return values needn't be described. Slightly incomplete in that it doesn't hint at what the verification result looks like, but it's sufficient for correct invocation.

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 100%, so commit, rolled_back, deployed_url and tool_version are already documented in structured fields. The description frames fix_ids as coming from geoa_pending_fixes, which is a small useful addition, but adds nothing for the optional parameters.

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 (report) and resource (approved fixes written and deployed to the site), and clarifies the effect: geoa re-fetches the public page to confirm. This clearly separates it from geoa_pending_fixes (which supplies the ids) and geoa_verify_claim.

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?

Gives a clear precondition: only report once the change is actually live, because 'a report made before the change is live stays unconfirmed.' It doesn't explicitly name sibling alternatives to use instead, but the when-to-use condition is unambiguous.

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