Skip to main content
Glama

Look up filter ids

qv_lookup
Read-onlyIdempotent

Look up valid filter IDs for legal searches: approving or executing bodies, subjects, types, statuses and lists. Returns each item's id and name for use in search queries.

Instructions

Find the ids that qv_search filters take: approving bodies, executing bodies, subjects, types, statuses, lists.

Returns items with id and name (plus count for approver, executor, subject).

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": {
      "kind": "<kind>"
    },
    "name": "qv_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesapprover (مرجع تصویب), executor (دستگاه مجری), subject (موضوع), type, status or list.
pageNoPages of 20 (approver, executor, subject).
queryNoName fragment, e.g. 'دیوان'. Empty lists the most used.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.2.1
    • changedInput schema / properties / kind / description
      Previous value: -"'approver' (مرجع تصویب), 'executor' (دستگاه مجری), 'subject' (موضوع), 'type' (نوع مصوبه), 'status' (وضعیت) or 'list' (curated lists)."New value: +"approver (مرجع تصویب), executor (دستگاه مجری), subject (موضوع), type, status or list."
    • changedInput schema / properties / page / description
      Previous value: -"Page of 20 for approver, executor and subject."New value: +"Pages of 20 (approver, executor, subject)."
    • changedInput schema / properties / query / description
      Previous value: -"Name fragment, e.g. 'دیوان' or 'بانک'. Empty lists the most used."New value: +"Name fragment, e.g. 'دیوان'. Empty lists the most used."
  2. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With readOnlyHint, idempotentHint, and destructiveHint=false already supplied, the safety profile is covered; the description instead contributes return-shape information (items carry `id` and name, plus `count` for approver/executor/subject) that is genuinely new since no output schema exists. It does not mention auth requirements, rate limits, or how `count` is computed, keeping it below a 5.

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?

Two short sentences: the first states the purpose and the enumerated kinds, the second states the return shape. Nothing is redundant and the key scoping information (what ids are for) is front-loaded.

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?

For a read-only lookup with a fully documented schema and no output schema, the description covers purpose and the essential return fields. Minor gaps remain — it does not clarify whether `query` applies to all kinds equally or what happens when a kind returns a large unpaginated list (type, status, list have no page parameter).

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% and the schema already explains the `kind` enum (including Persian glosses), the page size of 20, and the `query` name-fragment semantics with an example. The description only implies that results are filterable by kind and adds no extra syntax or constraints beyond what the schema states, so the baseline 3 applies.

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?

The description gives a specific verb+resource ("Find the ids that qv_search filters take") and enumerates the six kinds of filters covered (approving bodies, executing bodies, subjects, types, statuses, lists). It also explicitly frames the tool as the supplier of filter values for qv_search, so an agent can tell it apart from the search tool itself.

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

Usage Guidelines4/5

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

By stating the output is "the ids that qv_search filters take," it makes the intended workflow clear: resolve names to ids before filtering in qv_search. There is no explicit "do not use this to search laws" exclusion or statement of what to do if the query returns nothing, so it falls short of a full when/when-not treatment.

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