Skip to main content
Glama
Sign In
friends-mcp

friends-mcp

by ourostack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

describe_trust

Explain a friend's trust level and basis to clarify what interactions are permitted and constrained.

Instructions

Explain the trust context for a friend: level, basis (direct/shared_group/unknown), what it permits and constrains.

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": {
      "friendId": "<friendId>",
      "channel": "<channel>"
    },
    "name": "describe_trust"
  }
}

Input Schema

NameRequiredDescriptionDefault
friendIdYesfriend uuid or name
channelYesthe channel/sense for the explanation
isGroupChatNoset to 'true' when the conversation is a group chat

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.1

TDQS

A3.8/5.0
Behavior3/5

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

Without annotations, the description carries full burden. It states the read operation and output details but lacks disclosure on auth needs, side effects, or error behavior. Adequate but not comprehensive.

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?

Single well-structured sentence, front-loaded with verb, no wasted words. Efficiently communicates purpose and output.

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

Completeness4/5

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

No output schema, so description compensates by detailing return values (level, basis, permits/constrains). Basis includes possible values. Missing error handling mention but still fairly complete for a read tool.

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 covers all 3 parameters with descriptions. The description adds no extra meaning to parameters beyond what schema provides. Baseline 3 justified as schema does the work.

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 it explains trust context with specific elements (level, basis, permissions/constraints). It distinguishes from sibling tools like set_trust (write) and get_friend (general info).

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 reading trust context but provides no explicit guidance on when to use over alternatives like set_trust or channel_caps. No exclusions or when-not-to-use mentioned.

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