Skip to main content
Glama

Geoa — Get found in ChatGPT

Report Article Published

geoa_report_article_published
Idempotent

Report that a ready article is now published at a live URL. geoa starts measuring the article's effect on that URL and cross-links the other articles in its cluster to it. Without this, the article stays unpublished in geoa and keeps coming back as ready. 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": {
      "article_id": "<article_id>",
      "url": "<url>"
    },
    "name": "geoa_report_article_published"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe live URL the article is published at (https://…)
article_idYesThe article id from geoa_ready_articles

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, yet the description still adds substantive behavior: geoa starts measuring the article's effect on that URL, cross-links cluster articles to it, writes to the customer's geoa account, and requires sign-in. That is real side-effect disclosure an agent cannot get from the structured fields.

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?

Four short, front-loaded sentences that each carry information: action, consequences, failure mode, auth requirement. Minor redundancy between 'stays unpublished in geoa' and 'keeps coming back as ready', but no wasted phrasing.

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 could say what the call returns (e.g., confirmation or measurement status), which it omits. Otherwise it covers the mutation's effect, its idempotency implication, and the auth prerequisite, which is enough for a two-parameter mutation.

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 description coverage is 100% with only two parameters, so the schema already defines 'url' as the live https:// URL and 'article_id' as coming from geoa_ready_articles. The description adds no format, validation, or sourcing detail beyond that, so the baseline of 3 applies.

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 and resource ('Report that a ready article is now published at a live URL') plus the downstream consequences, so an agent immediately knows this transitions an article from ready to published. The article_id reference to geoa_ready_articles implicitly delineates it from the sibling that lists ready articles.

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 strong when-to-use trigger and a negative consequence for omitting it ('stays unpublished in geoa and keeps coming back as ready'), which is exactly the context an agent needs to decide whether to call. It stops short of explicitly naming alternatives such as geoa_report_fixes_live or stating when not to call (e.g., URL not yet live).

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