Skip to main content
Glama
Sign In
Proofpage MCP Server

Proofpage MCP Server

by Mehxeo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

proofpage_list_sources

Lists configured sources and their truthful access states to verify which web evidence sources are available for search and citation.

Instructions

List configured sources and truthful access states.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "proofpage_list_sources"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not disclose whether the operation is read-only, whether access states are live or cached, whether pagination applies, or what 'truthful' means in practice, leaving the agent with only a vague signal.

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?

A single short sentence with no filler, front-loading the action and resource. Nothing is redundant or buried.

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

Completeness3/5

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

The tool is simple (zero params, no output schema), but with no annotations and no return-shape documentation, the description should clarify what a 'source' record or 'access state' looks like and whether this is safe to call. It is minimally adequate but leaves real gaps for an agent deciding how to use the results.

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?

The tool takes zero parameters, so parameter semantics are not a concern; baseline is 4. The description appropriately does not waste space explaining an empty input schema.

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 clear verb ('List') and resource ('configured sources'), plus an extra returned facet ('truthful access states'). It is reasonably distinguishable from proofpage_add_source and proofpage_get_source_access, though the phrase 'truthful access states' is slightly opaque and could be confused with the dedicated get_source_access sibling.

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

Usage Guidelines2/5

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

No guidance on when to use this versus proofpage_get_source_access or other source-related siblings. Nothing states prerequisites, refresh behavior, or whether this is a discovery step before scheduling or adding sources.

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

Deploy Server

Other Tools