Skip to main content
Glama

FORUM scoring method metadata

get_method
Read-onlyIdempotent

Return the metadata of the scoring method behind the current FORUM release: method_version, as_of_input_date, record_count, merkle_root, the record hash_recipe and freshness thresholds (the same object as GET /v1/method on the FORUM HTTP API), plus pointers with SHA-256 to the full method document (/v1/method/doc; section 10 holds the verification recipes), the weights file and the release manifest, and the path of the signing keys. The method is public and versioned; weights live in a published config file. What a score is NOT: Not a security guarantee, not a penetration test, not certification of code correctness. It is a longitudinal behavioral-reputation summary with full evidence disclosure: scanners answer "is this safe to install today"; FORUM answers "what has this thing done since everyone installed it". Scores are flags, not verdicts: the band is derived only from the documented sub-scores, and a sub-score FORUM could not observe is reported as null with a reason, not estimated. Takes no arguments. Read-only.

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": "get_method"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the method is public and versioned, weights live in a published config file, unobservable sub-scores are reported as null with a reason rather than estimated, and SHA-256 pointers plus a signing-key path are exposed. That is meaningful disclosure an agent could not get from the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The field list and pointer inventory are front-loaded and useful, but the middle section drifts into product-positioning prose ('what has this thing done since everyone installed it', 'Scores are flags, not verdicts') that is longer than an agent needs for tool selection. The single dense opening sentence also packs many clauses together, making it harder to scan than a short bulleted inventory would be.

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?

With no output schema, the description carries the burden of describing return values, and it does so by enumerating the top-level fields and the SHA-256 pointers to the full document, weights file and manifest. It omits the concrete response shape or serialization details, but for a zero-argument read of a metadata object this is close to complete.

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, which sets the baseline at 4, and the description explicitly confirms 'Takes no arguments,' matching the empty schema with additionalProperties false. There is no parameter meaning left to add.

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?

The description names a specific verb and resource — returning the metadata of the scoring method behind the current FORUM release — and enumerates the fields returned (method_version, as_of_input_date, record_count, merkle_root, hash_recipe, freshness thresholds). That is far more precise than a restatement of the name. It does not, however, explicitly differentiate itself from the siblings get_proof or trust_lookup, so an agent must infer the boundary from the word 'metadata' alone.

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?

There is no explicit when-to-use guidance and no named alternative. The 'What a score is NOT' passage and the scanners-vs-FORUM contrast frame the overall product philosophy rather than telling an agent when to call this tool instead of get_proof or trust_lookup. 'Takes no arguments. Read-only.' describes invocation cost, not selection criteria.

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.