Skip to main content
Glama
@presencis/regulatory-mcp

@presencis/regulatory-mcp

Official

search_compliance_qa

Read-only

Search and rank public compliance Q&A by query, optionally filtered by regulation, and return canonical presencis.com question links.

Instructions

Rank public compliance questions. Returns canonical https://presencis.com/questions// links.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes
regulationNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuine value with "Returns canonical https://presencis.com/questions/<slug>/ links," which discloses the return shape in the absence of an output schema. It does not disclose ranking behavior, result ordering, or what happens when nothing matches, so it is helpful but thin.

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?

Two compact sentences with no filler, and the core action is front-loaded before the return-value note. Neither sentence is wasted, though the definition is arguably too terse for a three-parameter tool rather than bloated.

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

Completeness2/5

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

With no output schema and 0% schema description coverage, the description should explain both the parameters and the result set. It covers the return links briefly but leaves all three parameters and the ranking semantics undocumented, which is inadequate for a search tool with a regulation filter and a limit cap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across three parameters, so the description must carry the burden and largely fails. It never explains what query matches (keywords? full questions?), what regulation filters on (name, ID, slug?), or that limit is capped at 25 and defaults to something unspecified. "Public compliance questions" hints at the corpus but adds no per-parameter meaning.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Rank public compliance questions" gives a verb and a resource, and the name search_compliance_qa plus the required query parameter make it reasonably clear this is a search/ranking tool over Q&A content. However, "rank" is never tied explicitly to a search query, so the agent must infer that purpose from the schema rather than the prose. It does implicitly distinguish itself from the framework/crosswalk siblings, but without saying so.

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

Usage Guidelines2/5

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

There is no guidance on when to use this versus find_crosswalk, get_framework, list_frameworks, or map_sector_obligations, and no exclusions or prerequisites. The agent is left to infer that this is the Q&A retrieval path while the siblings cover frameworks and mappings.

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