Skip to main content
Glama
Sign In
AutoFYI MCP

AutoFYI MCP

by saiganeshreddy7
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

find_client

Read-onlyIdempotent

Search for a client by name; if no exact match exists, get ranked candidates for AI review and user confirmation.

Instructions

Load one strict identical client name; otherwise return ranked candidates for AI review and user confirmation.

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": "find_client"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes
detail_levelNosummary

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and non-destructive, so the safety profile is covered. The description adds useful behavioral context: strict identical matching and the fallback to ranked candidates for AI review and user confirmation, which is valuable beyond annotations.

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?

The description is a single, well-structured sentence that front-loads the main action and the fallback, with no redundant information. It is concise and fully earn its place.

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?

The tool has no output schema, and the description does not explain the structure of ranked candidates or the effect of 'detail_level'. While the core purpose is clear, missing parameter details and return format reduce completeness for a tool with only two parameters and no output schema.

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?

The schema has no descriptions (0% coverage), and the description only clarifies that 'query' refers to a client name. The 'detail_level' parameter is completely unexplained, leaving a significant gap in parameter understanding.

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

Purpose5/5

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

The description clearly states the tool loads an exact client name or falls back to ranked candidates, which is a specific verb+resource and distinguishes it from sibling search_clients by its strict-match behavior.

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?

The description implies usage when an exact client name is needed or when candidates require review, but it does not explicitly mention alternatives or when-not-to-use. The context is clear but not fully explicit.

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

Deploy Server

Other Tools