Skip to main content
Glama

get_intel_findings_search

Read-only

Use when researching tribunal precedent for a specific defect or claim type before filing or defending a construction claim. Returns findings filtered by defect family, claim type, outcome, owner, and keyword, with docket number and case name from the underlying decision. Example: differing-site-conditions findings against notice-and-time-bar defenses, 31% denial rate across 58 findi. Cryptographically attested with a post-quantum signed settlement receipt. Verify at trust.stratalize.com/verify. $0.02 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_intel_findings_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
keywordNoMatched against the finding summary
outcomeNogranted, denied, partial, or remanded
owner_idNo
claim_typeNo
defect_familyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds genuinely new behavior: the return payload includes docket number and case name from the underlying decision, and each call costs $0.02 USDC with an attestation/verification path — cost and provenance facts an agent cannot get from annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The usage condition and return shape are front-loaded, which is good. But the example sentence is truncated mid-word ('58 findi'), and the attestation/verification/pricing sentences read as marketing boilerplate that dilutes the operational content.

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?

With no output schema, the description does well to name the key returned fields (docket number, case name). It omits result volume, default limit behavior, and how to choose between the five free-form string filters, which matters for a 6-parameter, zero-required search 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?

Schema description coverage is only 33%, so the description must carry weight; it enumerates the filter dimensions (defect family, claim type, outcome, owner, keyword), which maps most parameters to meaning. However, it only restates parameter names rather than adding accepted value formats, and it is silent on 'limit', including defaults or caps.

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 specific verb (search/research) and resource (tribunal findings on construction defect claims) with the domain scope made explicit. It is clearly not a lettings, owner, or unit-price tool, though it never names the nearest sibling alternatives to differentiate against.

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?

'Use when researching tribunal precedent for a specific defect or claim type before filing or defending a construction claim' gives a concrete decision context, including the workflow stage. It stops short of exclusions or naming alternative tools for adjacent research needs.

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.

Resources