Skip to main content
Glama

Geoa — Get found in ChatGPT

Score Prospects (Radar)

geoa_radar_score_prospects
Idempotent

GEO-score the prospects in a Radar search (search_id from geoa_radar_find_prospects): healthy company + weak AI visibility = highest sales priority. Scoring runs in the background — call again with the same search_id to fetch results. 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": {
      "search_id": "<search_id>"
    },
    "name": "geoa_radar_score_prospects"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_idYesSearch id from geoa_radar_find_prospects

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: scoring is asynchronous and must be polled by re-calling with the same search_id, and a geoa account sign-in is required. These are exactly the operational facts the agent needs and cannot infer from readOnlyHint=false, idempotentHint=true, or openWorldHint=true.

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 the tool does, then the value heuristic, then the async/auth caveats. No sentence is filler and the critical polling instruction is not buried.

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 async lifecycle, auth prerequisite, and input provenance for a single-parameter tool with no output schema. What remains unstated is the shape/scale of the returned scores and whether re-scoring overwrites prior results — useful but not blocking 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?

With one parameter and 100% schema description coverage, the schema already defines search_id and its provenance, so the baseline is 3. The description reinforces the same point ('search_id from geoa_radar_find_prospects') and adds the polling semantics of reusing the id, but contributes no new format or constraint information.

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 verb and resource — 'GEO-score the prospects in a Radar search' — and explicitly points to geoa_radar_find_prospects as the source of search_id, which separates it from the discovery tool. However, the sibling geoa_geo_score also scores things, and nothing here distinguishes per-company scoring from batch Radar scoring, leaving one ambiguity for the agent.

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 selection heuristic ('healthy company + weak AI visibility = highest sales priority') and describes the follow-up call pattern. It does not state when to prefer geoa_geo_score or geoa_radar_enrich instead, but the input provenance makes the intended workflow evident.

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