Skip to main content
Glama
web-algebra-mcp

web-algebra-mcp

Official
by AtomGraph

Reconcile

Queries a W3C Reconciliation Service API endpoint with a name to return ranked candidate entities and their URIs, names, descriptions, scores, and match types, optionally filtered by type or limit.

Instructions

The entities a reconciliation service (the W3C Reconciliation Service API) offers for a name, as a result: one row per candidate, best first, binding ?entity (a URI), ?name, ?description, ?score and ?match. type is one of the service's type ids, limit caps the rows. Wikidata's service is https://wikidata-reconciliation.wmcloud.org/en/api, whose type ids are Wikidata items (Q515 city, Q6256 country, Q43229 organization).

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": {
      "endpoint": "<endpoint>",
      "query": "<query>"
    },
    "name": "Reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional: one of the service's type ids, e.g. Q515.
limitNoOptional: at most this many candidates.
queryYesThe name to reconcile.
endpointYesThe reconciliation service's URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.4

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does useful work by stating the result shape (candidate rows ordered best-first, binding ?entity, ?name, ?description, ?score, ?match) and that `limit` caps rows, but it says nothing about network behavior, failure modes when the endpoint is unreachable, or whether unknown endpoints are trusted.

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?

Everything said is relevant, but it is delivered as one dense run-on paragraph mixing purpose, result schema, parameter notes, and a concrete service example. It is front-loaded reasonably, but the long Wikidata URL and type-id list make it heavier than needed for a four-parameter tool.

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?

With no output schema and no annotations, the description must cover both return values and behavior. It covers the returned variables and ordering, which is the key gap-filler, but leaves the meaning of ?score and ?match, and the service's error/limit defaults, unexplained for a tool whose whole contract is a remote API call.

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 already 100%, so the baseline is 3, and the description adds genuine meaning: `type` is constrained to the service's own type ids with concrete Wikidata examples (Q515, Q6256, Q43229), `limit` is described as capping candidate rows, and a full example endpoint is given for `endpoint`.

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 states that it takes a name and returns candidate entities from a W3C Reconciliation Service API endpoint, with the result shape spelled out (one row per candidate, best first). The purpose is identifiable, though it is framed as a noun phrase ('The entities a reconciliation service offers') rather than a verb, and it does not explicitly differentiate itself from nearby tools such as ResolveURI.

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?

Usage is only implied: an agent can infer this is for resolving a free-text name to entity URIs against a reconciliation endpoint. There is no explicit when-to-use/when-not guidance and no named alternative for cases like resolving a known URI string. The Wikidata endpoint example is helpful context but is not guidance.

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