Skip to main content
Glama
bharatlas-mcp

bharatlas-mcp

moderate_record

Approve or reject one pending map point using its admin link and map id. Updates a record's status to published, rejected, or pending with an optional reason.

Instructions

Approve or reject one pending point (needs the admin link). Pass the map id it belongs to.

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": {
      "id": "<id>",
      "record_id": "<record_id>",
      "status": "<status>"
    },
    "name": "moderate_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe map (collection) id
reasonNo
statusYes
record_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden, and it only partly delivers: it notes the admin-link prerequisite, which is genuinely useful. It does not disclose the consequence of approving (presumably the point becomes publicly visible), whether rejection is reversible, or what the modifiable statuses actually do, so an agent cannot reason about effects before committing a mutation.

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?

Two short sentences, verb-first, with the prerequisite and the identifier requirement front-loaded. Nothing is wasted and nothing is buried.

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

Completeness2/5

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

For a four-parameter mutation with no annotations, no output schema, and 25% schema coverage, the description leaves too much open: the reason parameter's role, the meaning of the 'pending' status, and the post-moderation state of the record are all undocumented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 25%, so the description must compensate, and it clarifies id as the parent map id while implying record_id is the point being moderated. It never mentions the optional reason parameter at all, and the stated 'approve or reject' framing conflicts with the schema's additional 'pending' status value, leaving the status semantics ambiguous.

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 pair (approve/reject) and a specific resource (one pending point), which clearly separates it from siblings like publish or get_records. It stops short of saying where these pending points come from (list_submissions) or how it relates to the publish tool, so it is clear but not fully differentiated.

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?

Gives two useful constraints: it operates on exactly one point at a time, and it needs the admin link, which implicitly tells an agent this is an admin-only operation on a pending submission. It names no alternatives and does not say what to do instead when the point is already published or when multiple points need moderating.

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