Skip to main content
Glama

Geoa — Get found in ChatGPT

Approved Fixes Not Yet in the Code

geoa_pending_fixes
Read-onlyIdempotent

The approved geoa fixes that are NOT yet written into this site's code, for sites built or updated with Claude Code. Each item carries the path (url_pattern), the new value to write, and what geoa measured there before, so you can find the right spot in the repo. A human already approved every item in geoa before it appears here. Read-only. 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_pending_fixes"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds meaningful context beyond annotations: every item was human-approved in geoa, each item includes the path, new value, and prior measured value, and access requires sign-in.

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?

The description is four efficient sentences, front-loaded with the core definition and state, followed by item contents, approval provenance, and access requirements. No sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters, no output schema, and strong annotation coverage, the description is complete enough for correct invocation. It explains what the tool returns, the approval precondition, the auth requirement, and how the returned data helps locate the right repo location.

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 zero parameters, so there is no parameter semantics burden. The schema is empty and schema description coverage is 100%; the description correctly focuses on what the returned items contain rather than inventing input details.

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 state: approved geoa fixes that are not yet written into this site's code, scoped to sites built or updated with Claude Code. It is clear what the tool returns, though it does not explicitly distinguish itself from sibling tools like geoa_fix_backlog or geoa_report_fixes_live by name.

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?

Usage is implied: an agent can infer this tool is for retrieving approved fixes that still need implementation, and that it requires a signed-in geoa account. However, it does not say when to use this versus geoa_fix_backlog, geoa_report_fixes_live, or other siblings, nor does it state exclusions.

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