Skip to main content
Glama

Probative legal-market research

Rank states or counties by demand

rank_markets
Read-onlyIdempotent

Ranks the states (state "US") or one state's counties by one demand count for the practice. A count, not a score. Results are not legal advice.

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": {
      "state": "<state>",
      "practice": "<practice>"
    },
    "name": "rank_markets"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoen
limitNo
stateYesTwo-letter state code to rank its counties, or US to rank the…
metricNoOptional demand measure key (e.g.…
per100kNoRank by the count per 100,000 residents instead of the count
minValueNoLeave out units whose count is below this (small counts make…
practiceYesPractice id (personal-injury, truck-accidents, employment-law…

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-obvious semantics beyond them: results are raw counts rather than scores, and the output carries a legal-advice disclaimer.

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 short sentences with the core action front-loaded and no redundant restatement of the name. The trailing 'Results are not legal advice' is boilerplate, but it is brief and plausibly load-bearing for a demand-estimate 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?

An output schema exists and the annotations are rich, so the description needn't explain return values, and it adequately covers the state-scope decision. It is still missing explanations of sort order, what happens when `metric` is omitted, and the effect of `per100k`/`minValue`, which matter for correct invocation of a 7-parameter tool.

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?

With 71% schema description coverage the schema does most of the work. The description adds meaning for the `state` parameter's special 'US' sentinel (rank states vs that state's counties) but says nothing about `per100k`, `minValue`, `metric`, or `limit`, leaving the normalization and filtering behavior undocumented in prose.

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 concrete verb+resource ('Ranks the states ... or one state's counties by one demand count') and clarifies the output kind is a count rather than a score. It does not explicitly name the sibling compare_markets or market_profile as the alternative, so the differentiation is inferential rather than stated.

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?

The description implies usage through the 'state "US" vs a two-letter code' branching, which tells the agent how to pick state-level versus county-level ranking. It gives no explicit when-to-use/when-not guidance and never names compare_markets or supply_gap as alternatives for related questions.

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.