Maryland property-assessment fairness checks vs similar homes, with appeal windows and links.
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 4.2/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of confusing it with another. The tool's purpose is clearly defined.
The single tool uses a clear verb_noun convention (check_assessment), which is consistent even though there is only one name.
With a narrow domain (Maryland property assessment fairness), a single comprehensive tool is appropriate. It is under the typical tool count but reasonable for the server's focused purpose.
The tool covers the full lifecycle of an assessment fairness check: it evaluates the property, compares it to similar homes, provides a verdict, and supplies appeal information. It handles edge cases like multiple matches, so there are no obvious dead ends.
check_assessmentAInspectFairness check for a Maryland property assessment: where the address sits among genuinely similar homes (same reassessment group, similar size/lot/age, same zip), the group's median sales ratio, verdict branch (fair/review/elevated/insufficient), and Maryland's appeal windows with official filing links. If several parcels share the address, returns multiple_matches with account ids; re-call with acct.
| Name | Required | Description | Default |
|---|---|---|---|
| zip | No | 5-digit zip (recommended; addresses repeat across Maryland) | |
| acct | No | SDAT account id from a prior multiple_matches result (wins over address) | |
| address | No | Street address as the roll writes it, e.g. 1 STATE CIR (no unit numbers, no city) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure. It does this well by explaining the matching logic (same reassessment group, similar size/lot/age, same zip), the verdict branches, and the multiple_matches flow. It stops short of describing error conditions or handling of missing parameters, which would be a small addition.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with the core purpose and then provides essential detail in a compact two-sentence structure. No filler words; the multi-match re-call instruction earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
In the absence of an output schema, the description does a solid job of enumerating what the tool returns and how to disambiguate multi-parcel cases. A minor gap is that with all parameters optional, the description does not state what happens when no address/zip/acct is provided, but the overall context is sufficient for normal use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so per the guideline baseline is 3. The description repeats the acct re-call behavior already captured in the schema but adds no new parameter-level meaning beyond what the rich schema descriptions already provide.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'Fairness check for a Maryland property assessment.' It then enumerates concrete outputs (comparison group, median sales ratio, verdict branch, appeal windows), making the tool's function unambiguous even without siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
While there are no sibling tools to contrast against, the description provides clear procedural guidance: if multiple parcels match, it returns multiple_matches and instructs the agent to re-call with acct. It also explains the recommended zip usage indirectly through the schema, but the description itself could more explicitly state when to prefer this tool over a general property lookup.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!