Skip to main content
Glama

Stratalize Intelligence

Get Intel Findings Search

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.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safe-read profile is covered. The description adds genuinely useful behavior beyond that: what fields come back (docket number, case name), a concrete outcome distribution example, and a $0.02 USDC per-call cost. However, the "cryptographically attested post-quantum signed settlement receipt / verify at trust.stratalize.com/verify" claim is promotional and does not inform invocation, and nothing is said about result caps or pagination despite the unconstrained limit.

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 when-to-use trigger is correctly front-loaded and the filter list is compact. But the tail contains a truncated, cut-off example plus a marketing sentence and a payment line, and the mixed commercial/attestation content dilutes the operational core.

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?

For a 6-parameter, all-optional, no-output-schema search tool, the description does tell the agent what comes back (docket number, case name) and how to frame the query. It omits default result counts, what limit does, and whether filters combine as AND — gaps that matter more given no output schema and low schema coverage.

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 does name the filter dimensions (defect family, claim type, outcome, owner, keyword) in prose, which partially compensates. But it adds no meaning for limit or owner_id, gives no format hints beyond what the schema says for outcome and keyword, and the example's truncation ("58 findi.") leaves the illustrative value unclear.

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?

The definition states a concrete verb+resource: it returns tribunal findings on construction defects/claims, filtered by defect family, claim type, outcome, owner, and keyword, with docket number and case name. That is far more specific than the title. It stops short of 5 because it never names which sibling to use instead (e.g., get_case_law_synthesis or get_citation_authority look adjacent), leaving the agent to infer the boundary.

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 clear situational trigger, including the workflow moment (pre-filing/pre-defense). It provides no exclusions or alternative-tool routing, so it lands just below the top score.

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