Skip to main content
Glama
Sign In

Untax

by io.untax
OverviewDiscussionsAdmin

get_condition_evidence_catalog

Read-onlyIdempotent

Retrieve generic property-condition evidence checklists. Categories have not been screened for any property. No repair-cost, legal entitlement, market-value adjustment or tax deduction is established.

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_condition_evidence_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world behavior, so the description is not obligated to cover safety. It still adds substantive context beyond them: the categories are unscreened for any specific property, and the output establishes no repair-cost, legal, valuation or tax conclusions. That authority disclaimer is exactly the kind of behavioral context annotations cannot convey.

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 with no filler, and the operative description ('Retrieve generic ... checklists') is front-loaded ahead of the caveats. Every clause either states what is returned or limits how it may be used.

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 carries the burden of describing the return value, yet it only says 'checklists' and 'categories' without indicating their shape, grouping, or typical fields. It is adequate for a simple zero-parameter read but leaves the agent guessing what a returned checklist looks like.

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

Parameters4/5

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

The tool takes zero parameters, so the schema leaves nothing to explain and the baseline is 4. The description correctly spends no words on non-existent inputs.

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 description names a specific verb and resource: 'Retrieve generic property-condition evidence checklists.' An agent knows it gets a catalog of categories/checklists rather than property-specific findings. It does not explicitly contrast itself with the similarly named suggest_property_condition_defects, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

Usage is only implicit: the word 'generic' and the note that categories 'have not been screened for any property' signal this is a reference lookup, not a per-property analysis. The closing disclaimers carve out what the results cannot be used for (repair cost, legal entitlement, market-value adjustment, tax deduction), which is a useful boundary but not an explicit when-to-use/when-not/alternative statement.

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

All Untax toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources