Skip to main content
Glama
Sign In

Conciergr

by com.conciergr
OverviewDiscussionsAdmin

Set the Needs you topics

set_topics
Destructive

The kinds of work the Team Inbox sorts waiting chats into (for example New enquiry, Payment, Class change), so each person can take one kind. Up to 8 including Other, which is always last and added for you; names up to 30 characters. The whole list in order: keep a topic's id when renaming it so its chats stay with it.

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": {
      "topics": "<topics>"
    },
    "name": "set_topics"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoWhich assistant (its slug from get_overview `brands[].slug`). Leave out when the business has one.
topicsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already flag the operation as destructive and not read-only, and the description adds meaningful constraints: up to 8 topics, Other is always last and auto-added, names max 30 characters, and ids must be preserved when renaming so chats stay attached. It does not explicitly state what happens to chats of topics that are omitted or removed, which keeps it from a 5.

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?

The description is dense and well-structured, moving from definition to constraints to id preservation guidance. It is appropriately sized with no filler, though the opening is a noun-phrase definition rather than a direct action statement.

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 destructive full-list replacement tool with no output schema and partial schema coverage, the description covers most operational constraints. However, it does not clarify the consequence of omitting an existing topic, such as whether its chats are removed, reassigned, or moved to Other.

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 only 50%, but the description compensates well for the topics parameter by explaining the item limit, the special Other topic, name length, and the importance of preserving id on rename. The brand parameter is not covered in the description, but its schema description already explains it.

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 defines the resource precisely: topics are the work categories the Team Inbox uses to sort waiting chats. It also conveys that the tool supplies the whole ordered list, implying a set/replace operation. It stops short of an explicit action verb and does not differentiate the tool from siblings such as list_needs_you.

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?

Usage is only implied by the explanation that topics let each person take one kind of work. There is no explicit instruction on when to call this tool versus alternatives, and no prerequisites or exclusions are named.

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

All Conciergr toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources