Yuppsy

agent_search_by_name

Get real estate agent by First and Last Name.

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": {
      "firstName": "<firstName>",
      "lastName": "<lastName>"
    },
    "name": "agent_search_by_name"
  }
}

Input Schema

Name	Required	Description	Default
`lastName`	Yes	The agent last name.
`firstName`	Yes	The agent first name.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 5, 2026
- addedInput schema / properties / firstName / description
```
Added value: +"The agent first name."
```
- addedInput schema / properties / lastName / description
```
Added value: +"The agent last name."
```
First observedOct 22, 2026

TDQS

B3.2/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden, and it discloses almost nothing beyond the operation itself. It does not say whether matching is exact or partial, case-sensitive, whether multiple agents can be returned, or what an empty result means — all material for a name-based lookup.

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

Conciseness4/5

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

A single short sentence with no filler, and the key information is front-loaded. It is minimal but nothing is wasted.

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 two-parameter read tool with full schema coverage and no output schema, the description is minimally sufficient to call it. The notable gap is return cardinality — whether a name search yields one agent or a list — which matters for ambiguous names.

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 100%, so both parameters are already documented in the schema and the baseline is 3. The description only restates that the parameters are first and last name, adding no format, casing, or matching semantics.

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 states a specific verb and resource ("Get real estate agent") plus the lookup key (first and last name), which separates it from agent_get_by_id. It does not explicitly name that sibling, but the lookup-by-name scope is clear.

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 implied: an agent can infer this is the name-based lookup among the agent_* family. There is no explicit statement of when to prefer it over agent_get_by_id (when an ID is known) or any note on prerequisites such as exact-name matching.

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

All Yuppsy tools Inspect

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

Need Help?