Skip to main content
Glama

Suggest Angles

suggest_angles

[Read · 5 credits] Given a topic, suggest distinct content angles informed by what performs well in the user's scoped data. Pulls top-performing historical posts as context and calls OpenAI to generate 5 concrete angles. Costs 5 credits per call. Pass profile_id to scope to a tracked profile, collection_id to scope to a collection, or neither to use the user's full library.

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

Input Schema

NameRequiredDescriptionDefault
topicYesTopic or theme to generate angles for (e.g. 'onboarding new hires', 'pricing strategy')
profile_idNoOptional tracked profile ID (scopes to this profile's posts)
collection_idNoOptional post_collections.id (scopes to this collection's members)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing the 5-credit cost, the OpenAI call, and the historical-post context that shapes output. That credit-charging side effect also explains why readOnlyHint=false despite the '[Read · ...]' tier label, though the tension between that label and the annotation is not spelled out. No latency, rate-limit, or failure behavior is mentioned.

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?

Cost and read-only tier are front-loaded in brackets, and the body moves topic → mechanism → scoping in a single readable paragraph. The 5-credit cost is stated twice ('[Read · 5 credits]' and 'Costs 5 credits per call'), which is the only redundant wording.

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?

For a 3-parameter generative tool with no output schema, the description covers input scoping and return shape ('5 concrete angles'). The remaining gap is edge-case behavior: mutual exclusivity of the two scope IDs and what happens on insufficient credits or an OpenAI failure.

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 adds meaning the schema does not: the default when neither scope parameter is supplied ('the user's full library'). It stops short of saying whether profile_id and collection_id may be combined or which wins if both are passed.

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?

Names a specific action and output ('suggest distinct content angles') plus how it is produced ('pulls top-performing historical posts as context and calls OpenAI to generate 5 concrete angles'). That distinguishes it from insight-retrieval siblings such as get_topic_insights or get_posting_insights, which surface data rather than generate new angles.

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?

Gives explicit scoping guidance: pass profile_id for one profile, collection_id for a collection, or neither for the full library. What is missing is any exclusion or sibling routing — nothing says when to prefer get_topic_insights or get_posting_insights over generating angles.

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