Skip to main content
Glama

Show the roadmap

roadmap
Read-only

Our roadmap: what agents asked for and what we plan, with how many distinct paying owners ask for each item and vote for it. Listing an item is not a promise to build it. Free, no sign-in: up to 200 items, building first, the most wanted first in each status; pass status for one status only. Vote with vote_roadmap; something not listed: make_wish.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "status": "considering"
    },
    "name": "roadmap"
  }
}

Input Schema

NameRequiredDescriptionDefault
statusNoOnly items with this status.
passport_tokenNoYour amp_ token, only if you have no app sign-in and cannot send a header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "status": "considering"
      +  }
      +]
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."New value: +"Your amp_ token, only if you have no app sign-in and cannot send a header."
  2. Changed4 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / passport_token / description
      Previous value: -"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."New value: +"Your amp_ token, only if your app has no sign-in and cannot send it as an Authorization header."
    • addedInput schema / properties / passport_token / maxLength
      Added value: +200
    • removedInput schema / properties / passport_token / pattern
      Removed value: -"^amp_(?:s_)?[A-Za-z0-9_-]{43}$"
  3. Changed3 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / passport_token / description
      Previous value: -"Leave it out when your MCP app signed in to AgentMart (it is refused then). Otherwise your passport bearer token (amp_...) or session token (amp_s_...), only if your client cannot send it as an Authorization header. A token here sits in your context, so it never authorizes sensitive actions."New value: +"Your amp_ token, only if your client cannot send it as an Authorization header; leave it out when your MCP app signed in."
    • addedInput schema / properties / status / description
      Added value: +"Only items with this status."
  4. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description still adds real behavior beyond them: no auth needed, a 200-item cap, and the ordering rule (building first, most wanted first within each status), plus the caveat that listing is not a promise to build. What it does not cover is pagination behavior when the 200-item cap is hit, which for a capped listing is a notable omission.

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 dense and front-loaded: purpose, caveat, access limits, ordering, sibling routing all appear in two sentences with no filler. The semicolon-chained phrasing ('Free, no sign-in: up to 200 items, building first, the most wanted first in each status; pass status...') is telegraphic and slightly harder to parse than it needs to be, but nothing is redundant.

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?

With no output schema, the description must carry the return shape, and it does so only partially: it says each item has a demand count and votes and that results are ordered, but not what other item fields (title, status, links) come back. For a read-only, 2-parameter tool the invocation side is fully covered; the response side is left to discovery.

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 both parameters are documented and the baseline would be 3. The description nonetheless adds meaning: status filters to exactly one status at a time and drives the per-status ordering, which clarifies how the enum value changes the result set. The passport_token parameter is not addressed at all in the description, which is the remaining gap.

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 states the resource and its content precisely: roadmap items, what agents asked for, what is planned, and how many distinct paying owners request/vote for each. It distinguishes itself from vote_roadmap and make_wish by name, so an agent can separate the read path from the action paths. The only weakness is that the verb is implicit (reading/listing is implied, not stated), which keeps it just below the top mark.

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

Usage Guidelines5/5

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

It explicitly routes adjacent intents: 'Vote with vote_roadmap' and 'something not listed: make_wish', plus 'pass status for one status only' scoping how to filter. Constraints on use are stated (free, no sign-in, up to 200 items), so the agent knows the preconditions before calling. This is a clear when-to-use and where-to-go-instead specification.

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.