Skip to main content
Glama

Confirm a page was checked by hand

acknowledge-hosted-self-check

Record that a person has checked a hosted page the automated fact check never read, as an attestation against the credential's user. The page can then be approved from the dashboard; this does not approve or publish it. Needs a user-tied write credential. Confirm someone has actually read the page.

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>"
    },
    "name": "acknowledge-hosted-self-check"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesHosted page ID from list-hosted-pages

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. Changed2 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • 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.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds meaningful context beyond them: the write is an attestation tied to the credential's user, requires a user-tied write credential, and explicitly does not approve or publish the page. This clarifies scope of effect and prerequisites, though it does not describe the response or any state-transition details on success.

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 description is three sentences and front-loads the core purpose immediately. The final sentence ('Confirm someone has actually read the page') is somewhat redundant with the first, but overall it is efficient and well-structured.

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 simple one-parameter mutation with full schema coverage and annotations, the description covers purpose, prerequisite credentials, and what the tool does not do. It could be slightly richer about the resulting state (e.g., what changes after acknowledgment), but no output schema exists and the core invocation context is present.

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?

There is only one parameter, page_id, and the schema already documents it at 100% coverage with a reference to list-hosted-pages. The description adds no additional parameter semantics (e.g., format, source, or constraints), so it sits at the baseline for high schema coverage.

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?

The description states a specific verb and resource: 'Record that a person has checked a hosted page the automated fact check never read, as an attestation against the credential's user.' It explicitly distinguishes the action from approval or publishing, which separates it from siblings like reject-hosted-page or publish-article. An agent can tell what this tool does without opening 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 Guidelines4/5

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

It clearly states the triggering condition ('the automated fact check never read' the page) and an exclusion ('this does not approve or publish it'), which routes the agent away from approval tools. However, it does not name specific alternative siblings (e.g., reject-hosted-page) for adjacent actions, so it falls short of explicit alternative routing.

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