Skip to main content
Glama
Sign In

Conciergr

by com.conciergr
OverviewDiscussionsAdmin

Scheduled messages

list_scheduled
Read-only

What the assistant will send next (follow-ups, reminders, check-ins), for one chat or all, each with its time, and the ones cancelled from the Team Inbox.

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

Input Schema

NameRequiredDescriptionDefault
brandNoWhich assistant (its slug from get_overview `brands[].slug`). Leave out when the business has one.
contactNoThe chat's contact key, from list_chats, list_needs_you or search_chats (`contact`).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false. The description adds useful context that cancelled scheduled messages are included and each has a time, but it does not cover return shape, ordering, or rate limits.

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?

It is a single efficient sentence with the core scope front-loaded. The phrase 'from the Team Inbox' is slightly ambiguous but not wasteful.

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 simple read-only list tool with two optional parameters and no output schema, the description covers what is listed and that times/cancelled items appear. It still lacks ordering, limits, or more concrete return expectations.

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 the schema fully documents brand and contact. The description only broadly indicates filtering by one chat or all, without adding syntax or semantics beyond the schema.

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 identifies the specific resource (scheduled messages the assistant will send) and scope (one chat or all, including cancelled ones). It is clear enough to distinguish from cancel_scheduled, though it does not explicitly name alternatives.

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 implied by 'for one chat or all' and by the mention of cancelled messages, but there is no explicit when-to-use guidance or comparison to siblings such as cancel_scheduled or list_chats.

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