Skip to main content
Glama

Plures

Find how people decided similar cases

find_precedents
Read-only

Searches the developer's judgment graph: past decisions people made on cases like this one, closest first, with the answer and how strongly they agreed. Returns a suggestion only when the case is settled: several close cases with the same options, all decided the same way with strong agreement. Free. To act on a settled case and have it recorded and billed as a decision, call ask_humans with use_precedent instead.

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": {
      "question": "<question>"
    },
    "name": "find_precedents"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoOnly this app. Default: PLURES_APP, then all apps
limitNoHow many past decisions to return. Default 5
contextNoThe material to judge, as plain text
optionsNoThe possible answers; a suggestion needs past cases with the same options
categoryNoOnly cases with this category
questionYesThe decision, worded as you would ask it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only say readOnlyHint=true and openWorldHint=true; the description adds real value on top: ranking order (closest first), the settlement criteria that gate the suggestion, that the call is free versus the billed ask_humans path, and what the results contain. It falls short of 5 only because it does not say what is returned when the case is not settled (empty suggestion vs. a raw list).

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?

Three sentences, front-loaded with the verb and resource, and the alternative-tool routing comes last where it belongs. Dense but every clause carries information; the first sentence is long and could be split for scanability.

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 correctly takes on the return-value burden by naming what comes back (the answer and agreement strength). For a read-only search tool with fully documented parameters this is close to complete; only the non-settled return case is left implicit.

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?

Schema coverage is 100%, so all six parameters are already documented in the schema. The description adds the useful linkage that a suggestion requires past cases with the same options, but gives no extra guidance on context, category, or app scoping beyond what the schema states. Baseline 3 applies when the schema does the heavy lifting.

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 ('searches the developer's judgment graph') plus the return shape ('past decisions ... closest first, with the answer and how strongly they agreed'). It also distinguishes itself from ask_humans by describing that tool's role, so an agent can tell the two apart without opening a 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 an explicit condition under which a suggestion is produced ('only when the case is settled: several close cases with the same options, all decided the same way with strong agreement') and an explicit alternative for the follow-up action ('call ask_humans with use_precedent instead'). When-to-use and what-to-do-next are both spelled out.

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.