Skip to main content
Glama

Find people and organizations

find_people
Read-only

People and organizations on GitHub (by name) and Hugging Face (by exact account name), with a link to their page on Take My Repo listing their public projects or models.

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

Input Schema

NameRequiredDescriptionDefault
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and external-call profile is known. The description adds useful behavioral context: it queries two distinct external services with different matching rules and returns a link to a curated project/model listing. It says nothing about auth, rate limits, multiple matches, or empty results.

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 tightly packed sentence with the sources and result content front-loaded; nothing is redundant. The parenthetical qualifiers slightly compress what could be clearer, but no sentence 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 one-parameter read-only lookup with annotations covering safety, the definition covers sources, matching semantics, and part of the return value. With no output schema, it should still say whether multiple people/orgs can be returned and what the result set looks like when a name is ambiguous.

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 coverage is 0% for the single `query` parameter, so the description must carry the burden. It does add real meaning: matching is by *name* on GitHub but by *exact account name* on Hugging Face, which is non-obvious and operationally important. It still omits whether URLs/handles are accepted and what happens on ambiguous matches.

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 the concrete resources (people and organizations), the two upstream sources (GitHub, Hugging Face), and an extra returned artifact (a Take My Repo link listing public projects or models). That is specific enough to distinguish this lookup from generic resource tools. It does not explicitly contrast with the sibling `search`, leaving a small ambiguity about scope.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative is named — notably `search`, which an agent could plausibly confuse with this lookup. Usage must be inferred entirely from the resource description.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources