Skip to main content
Glama

Geoa — Get found in ChatGPT

Articles Ready to Publish

geoa_ready_articles
Read-onlyIdempotent

Content Studio articles that are approved and ready to go into the site: title, body (markdown and HTML), meta description, FAQ, JSON-LD and the EU AI Act disclosure, for sites built or updated with Claude Code. 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_ready_articles"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 description's 'Read-only' restates structured data. It does add genuinely new behavior: sign-in to a geoa account is required. It says nothing about ordering, pagination, or what an empty result means.

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 front-loaded sentence identifies the resource and its state, then the field list follows. The field enumeration is long but earns its place because no output schema exists; the trailing site/Claude Code framing is the weakest clause.

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 and no parameters, the description carries the return-shape burden and does so reasonably by naming the fields returned. What remains missing is scope information: whether this returns all ready articles or a capped page, and in what order.

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?

Zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description instead spends its words on the returned fields, which is the right use of space for a no-arg tool.

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?

States a specific resource and state filter: 'Content Studio articles that are approved and ready to go into the site,' and enumerates the payload (title, body in markdown/HTML, meta description, FAQ, JSON-LD, EU AI Act disclosure). That is far more specific than the title alone, though it never explicitly says it returns a list or how many.

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 only implied by the 'approved and ready' qualifier; there is no explicit when-to-use or when-not-to-use. Notably the natural handoff sibling, geoa_report_article_published (publish then report), is never mentioned, so the agent must infer the workflow itself.

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