Skip to main content
Glama
Sign In
Rephonic

Rephonic

Official
by getrephonic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_interests

Retrieve common listener interests to use with the interests search filter. Optionally filter interests by name.

Instructions

Returns common listener interests, optionally filtered by name. These names are used with the interests search filter.

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

Input Schema

NameRequiredDescriptionDefault
queryNoFilter interests by name.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It indicates a read operation returning interests, but lacks details on auth, rate limits, pagination, error handling, or result ordering. The description is adequate for a simple list tool but could be more explicit.

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?

Two concise sentences with no wasted words. The first sentence front-loads the main purpose, and the second provides immediate context for usage.

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?

No output schema, but the description explains the purpose and usage context. However, it does not specify return format (e.g., array of strings), ordering, or limits. For a simple list tool, it is moderately complete but could be improved.

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 100%, so the schema already documents the 'query' parameter. The description adds context that results are used with the 'interests' filter but does not provide additional semantic meaning beyond filtering. Baseline 3 is appropriate.

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 the tool returns common listener interests, optionally filtered by name, and explicitly mentions their use with the 'interests' search filter. This distinguishes it from sibling list tools like list_sponsors and list_categories.

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

Usage Guidelines4/5

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

The description implies usage context by stating the returned names are used with the 'interests' search filter, guiding the agent on when to call this tool. However, it does not explicitly state when not to use it or compare alternatives among 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