Skip to main content
Glama
IBazylchuk

Paparats: Local Semantic Code Search

by IBazylchuk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

List Architecture Cards

arch_list
Read-only

Enumerate every architecture card in a group for audit, dedupe, or migration without vector search or ranking—use when you need ground truth, not top-N similarity.

Instructions

Enumerate arch cards in a group — no vector search, no ranking, no similarity threshold. Use this when you need every card (audit, dedupe, migration) rather than the top-N most similar to a query. arch_context is for relevance-ranked retrieval; arch_list is for ground truth.

Optional filters:

  • project: components must match this project (hard filter); decisions/lessons match this project OR have no project field (soft filter — group-wide guidance still surfaces).

  • kinds: subset of ['component', 'decision', 'lesson'].

  • include_history: include superseded/deprecated cards (default false).

  • limit (default 50, max 200), offset: pagination — pass next_offset from the previous response to resume.

Returns each card with id, kind, project (or 'global'), status, and a short label (name/title/rule). Use the ids with arch_delete or as input to follow-up arch_record_* calls (e.g. supersedes on arch_record_decision).

Input Schema

NameRequiredDescriptionDefault
groupYesGroup to list cards from.
kindsNoOptional. Restrict to a subset of card kinds.
limitNoOptional. Page size, default 50, max 200.
offsetNoOptional. Resume cursor from a previous call (`next_offset`). Pass the value verbatim — strings that look like JSON (start with `{` or `[`) are parsed back to the structured form Qdrant emits. Omit for the first page.
projectNoOptional. Restrict to one project. Components must match this project (hard filter); decisions and lessons match this project OR have no project field (soft filter, so group-wide guidance still surfaces).
include_historyNoOptional. Include superseded/deprecated cards. Default false.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

The annotations already declare a read-only, closed-world operation, but the description adds important behavioral context: there is no vector search or ranking, `project` filtering is hard for components and soft for decisions/lessons, and history is excluded by default. It also describes pagination and returned fields. Minor gaps like error behavior are not material for this list operation.

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?

The description is front-loaded with the core distinction and use cases, then lists optional filters and return/id usage compactly. Every sentence contributes actionable information without redundant restatement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, and the description compensates by explaining the returned card fields and how to use returned ids with `arch_delete` or `arch_record_*` calls. Combined with usage guidance, filter semantics, pagination, and annotation-covered safety profile, it provides enough context to invoke the tool correctly.

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 100% schema description coverage, the schema already explains each parameter, so the baseline is 3. The description reinforces the hard/soft `project` filter semantics and the pagination resume pattern, but it largely repeats structured parameter documentation rather than adding substantial new meaning.

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 states a specific verb and resource: enumerate arch cards in a group. It explicitly distinguishes this from vector search, ranking, similarity thresholds, and the sibling `arch_context`, so an agent can identify the tool's role without opening schemas.

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?

It gives explicit when-to-use guidance: audit, dedupe, migration, or any need for every card rather than top-N similarity results. It names the alternative `arch_context` and explains that it is for relevance-ranked retrieval while `arch_list` is for ground truth.

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

Deploy Server

Other Tools