Skip to main content
Glama
Reviewmetric
by vktr93

place_on_atlas

Maps a completed review’s manuscript onto the ReviewMetric Atlas to reveal its topic, cited landmarks, nearest discoveries, and research frontier.

Instructions

Where one of the user's reviewed manuscripts sits on the ReviewMetric Atlas: its topic, the landmarks it cites, the closest discoveries, and the frontier ahead of it.

Args: run_id: The Run ID of a completed review (see list_my_reviews).

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": {
      "run_id": "<run_id>"
    },
    "name": "place_on_atlas"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.2.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are present, so the description carries the full behavioral burden. It implies a read-only analytical lookup and hints at the return content, but says nothing about cost/latency, whether it mutates anything, or failure modes for an invalid/incomplete run_id.

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?

The prose lead is front-loaded and vivid but still economical; the Args block is a single line and earns its place by anchoring the one required parameter. Only mild redundancy with the output schema.

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 one required parameter and an output schema, the description needs only to name the operation, constrain the input, and point to the source of run_id — all of which it does. Nothing required for correct invocation is missing.

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?

Schema coverage is 0%, so the description must compensate, and it does: run_id is constrained to a completed review and the agent is pointed at list_my_reviews to obtain it. It stops short of format/validation 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?

States a specific verb+resource: it places one of the user's reviewed manuscripts on the ReviewMetric Atlas and describes the resulting facets (topic, cited landmarks, closest discoveries, frontier). Distinguishes it reasonably from siblings like search_atlas or list_frontiers, though it never explicitly names an alternative.

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?

Implicitly scoped by 'one of the user's reviewed manuscripts' and 'a completed review', and it routes the agent to list_my_reviews for the run_id. It does not say when to use this instead of search_atlas/trace_path, nor what happens if the review is incomplete.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.