Skip to main content
Glama
Sign In
friends-mcp

friends-mcp

by ourostack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

list_friends

Retrieve friend records with optional filters for trust level (family, friend, acquaintance, stranger) and kind (human, agent), and limit the number of results.

Instructions

List friend records, optionally filtered by trust level and kind, optionally limited.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_friends"
  }
}

Input Schema

NameRequiredDescriptionDefault
trustNofilter by trust level: family/friend/acquaintance/stranger
kindNofilter by kind: human/agent
limitNomax number of records to return

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

B3.2/5.0
Behavior2/5

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

There are no annotations, so the description bears full responsibility for behavioral disclosure. It only states the action and optional filters, omitting details like default behavior when no filters are applied, pagination, permissions, or output format. This leaves significant gaps for an AI agent.

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 sentence of 13 words, front-loading the core action and parameters. Every word is necessary, and there is no redundancy or fluff.

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

Completeness2/5

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

With no output schema, the description should clarify the return value (e.g., list of full friend records). It does not. Additionally, it fails to explain how filters interact (and, or) or what the default limit is, leaving the tool underspecified for reliable use.

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 baseline is 3. The description adds no new parameter meaning beyond the schema—it merely restates the optional filters and limit without providing context on defaults, interdependencies, or examples.

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 states a specific verb ('list'), a clear resource ('friend records'), and optional filters (trust, kind, limit), which clearly communicates the tool's purpose and differentiates from siblings like 'get_friend' that likely retrieves a single record.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., get_friend, set_trust, search tools). The description implies usage only by stating the action, leaving the agent to infer context from the tool name and siblings.

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