Skip to main content
Glama
Sign In

SelfBadge

by com.selfbadge
OverviewDiscussionsAdmin

Find a person by name

find_person
Read-only

Search SelfBadge for people with a given name. Use this to identify a person correctly and tell them apart from namesakes: each candidate comes with their job title, organization, location and a short description. Pass what you already know (job title, organization, location) so the best match comes first, then call get_person with the chosen id for the full, verified profile. It returns public SelfBadge profiles, each marked claimed or created from public sources (seeded: level 0, unconfirmed until the person claims it). An empty result means SelfBadge has no public profile with that name, not that the person does not exist.

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": {
      "name": "<name>"
    },
    "name": "find_person"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesThe person's full name, for example "Noa Bergman".
limitNoOptional. How many candidates to return (default 10).
locationNoOptional. A city or country you associate with them.
job_titleNoOptional. What you know of their job title, for example "Managing Partner".
organizationNoOptional. An organization you associate with them, for example "Harbor Ventures".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already establish readOnlyHint and openWorldHint=false, but the description adds real behavioral context: each candidate carries job title, organization, location and a short description, and results are marked claimed versus seeded (level 0, unconfirmed). It also explains result ordering and the meaning of an empty result, which is not derivable from structured fields; it stops short of covering result caps or auth details.

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?

Four sentences, each carrying distinct information, with the core action front-loaded in sentence one. The middle sentences are dense (return fields, ranking advice, claimed/seeded status, empty-result caveat) but none is redundant, so it stays readable without padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description carries the return-value burden and does so: it names the fields returned per candidate, the claimed/seeded status semantics, and the empty-result interpretation. Combined with the explicit hand-off to get_person, an agent has everything needed to call it correctly.

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?

Schema coverage is 100%, so the baseline is 3, but the description goes beyond the schema by explaining the effect of the optional filters: passing known job title, organization or location makes "the best match comes first," i.e. they act as ranking signals rather than hard filters. The limit parameter is left to the schema.

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 first sentence gives a specific verb and resource ("Search SelfBadge for people with a given name") and the description explicitly contrasts itself with the sibling get_person, which is the full-profile follow-up. An agent can distinguish it from get_person and get_organization without opening any schema.

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

Usage Guidelines5/5

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

It states exactly when to use this tool ("to identify a person correctly and tell them apart from namesakes"), names the alternative to call afterwards ("then call get_person with the chosen id for the full, verified profile"), and gives an exclusion-style caveat that an empty result means no public profile rather than a non-existent person.

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

All SelfBadge 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