Skip to main content
Glama

Decide a flagged claim

dispose-hosted-claim
Destructive

Record a decision on one claim a fact check flagged on a hosted page: accepted (true as written) or rejected (wrong). Every flagged claim must be decided before approval, and a rejected one blocks it. claim_index comes from get-hosted-page. Needs a user-tied write credential. Confirm with the user first.

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": {
      "page_id": "<page_id>",
      "claim_index": "<claim_index>",
      "disposition": "<disposition>"
    },
    "name": "dispose-hosted-claim"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesHosted page ID from list-hosted-pages
claim_indexYesPosition of the claim in unverified_claims.claims
dispositionYesaccepted: true as written. rejected: wrong.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / page_id / description
      Previous value: -"Hosted page ID"New value: +"Hosted page ID from list-hosted-pages"
  2. Changed3 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / claim_index / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / page_id / pattern
      Added value: +"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known; the description adds real value beyond that by disclosing the downstream consequence of rejection (blocks page approval) and the credential requirement. It stops short of covering reversibility — whether an existing decision can be changed or overwritten — which matters for a destructive write.

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 tight sentences with zero filler; the action and its outcomes come first, then the workflow constraint, then the operational prerequisites. Every clause carries distinct, actionable information.

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?

For a 3-parameter destructive mutation with full schema coverage, no output schema, and annotations present, the description covers purpose, workflow ordering, auth, and confirmation. It omits only edge-case behavior (re-deciding a claim, error responses), which is a minor gap rather than a blocker.

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 100%, so the baseline is 3 and the schema already defines all three parameters and the disposition enum values. The description still contributes provenance guidance ('claim_index comes from get-hosted-page') and restates the disposition semantics in plain language, a small but genuine increment over the structured fields.

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: 'Record a decision on one claim a fact check flagged on a hosted page', with the two allowed outcomes spelled out inline. The claim-level scope (not page-level) distinguishes it from the page-oriented siblings like reject-hosted-page without needing the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use conditions ('Every flagged claim must be decided before approval'), the consequence of a rejected outcome ('blocks it'), where the claim_index originates ('get-hosted-page'), the auth prerequisite ('user-tied write credential'), and a confirmation policy ('Confirm with the user first'). Nothing material is left to inference.

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