Skip to main content
Glama
Sign In

Subo

by gg.subo
OverviewDiscussionsAdmin

Trigger AI analysis

trigger_analysis

Summarize open-text answers with AI. Spends the community's AI credits and runs in the background — read the result with get_analysis, do not expect it in this reply. force re-summarizes blocks that already have a summary, at full cost. Refused with text_analysis_off when no open_text block may be summarized (community, project and block settings); get_analysis shows each block's text_analysis and why.

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": {
      "project_id": "<project_id>"
    },
    "name": "trigger_analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNoRe-summarize blocks that already have a summary. Costs credits again.
project_idYesProject id, from list_projects or create_project.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / force / description
      Added value: +"Re-summarize blocks that already have a summary. Costs credits again."
  2. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare the mutation profile (readOnlyHint=false, idempotentHint=false), and the description goes well beyond them: it discloses credit spend, asynchronous background execution, the extra cost of `force`, and the specific error condition tied to community/project/block settings. That is exactly the behavioral context annotations cannot carry.

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?

Three tight sentences with zero filler, front-loaded with the action, then the cost/async warning, then the edge-case refusal. Every clause carries decision-relevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, and the description compensates by redirecting to get_analysis for results and per-block `text_analysis` status. For a 2-parameter background job, nothing an agent needs to call it correctly is missing.

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% and already documents both parameters, so the baseline is 3. The description still adds value by framing `force` as a full-cost re-summarization and by tying the failure mode to block-level `text_analysis` settings visible in get_analysis.

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?

Opens with a specific verb and resource: 'Summarize open-text answers with AI.' It also immediately names the sibling that holds the result (get_analysis), so an agent can separate triggering from reading without inspecting either 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 says not to expect the result in the reply and to call get_analysis instead, and explains when to set `force` (blocks that already have a summary, at full cost). It also documents the refusal path (`text_analysis_off`) and where to diagnose it.

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

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