Skip to main content
Glama
Sign In

SuprSend

by com.suprsend
OverviewDiscussionsAdmin

List schemas

schemas_list
Read-onlyIdempotent

Finds trigger schemas by text in the name, slug, or description, or lists all of them: JSON Schemas that check the data of workflow triggers and events. Use schemas_get for the JSON Schema itself; schemas_save_draft and schemas_publish to change one.

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": {
      "workspace": "<workspace>",
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "schemas_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNolive (default): schemas with a published version. draft: all schemas.live
limitNoItems per page (1–100).
offsetNoItems to skip (the paging note of the previous page gives it).
searchNoText to find in the name, slug, or description.
contextYesAnalytics: why you call this tool, in 10-20 words. Say "a user", never names, emails, or IDs.
llm_modelYesAnalytics: your model ID, or "unknown".
workspaceYesThe slug of the workspace to act on. Call workspaces_list to find the valid values.
conversation_idNoPass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Output Schema

NameRequiredDescriptionDefault
metaYes
resultsYes
_mcp_instructionsNoServer-issued metadata for this conversation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful domain context about what a schema is, but says nothing about pagination behaviour or result-shaping beyond what the schema documents.

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 sentences, zero padding, with the core action front-loaded and the routing guidance second. Every clause earns its place.

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?

Given an output schema exists and annotations carry the safety profile, the description supplies enough for an agent to pick and call this tool. Only a brief note on the live/draft distinction would have made it fully complete.

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 parameters are fully documented structurally. The description only restates the search behaviour (name, slug, description) and never mentions the meaningful mode=live/draft or limit/offset semantics, so it adds little beyond the schema.

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?

States a specific verb (finds/lists) and resource (trigger schemas), and defines the resource as 'JSON Schemas that check the data of workflow triggers and events'. It also names the sibling tools for reading and mutating a schema, so it is distinguishable from them without opening a schema.

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?

Explicitly routes: use this to search/list, schemas_get for the JSON Schema itself, and schemas_save_draft/schemas_publish to change one. That covers the alternatives and the conditions that select them.

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

All SuprSend 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