Skip to main content
Glama

Analyze

analyze
Read-only

Analyze token savings, audit agent costs, and generate AEO reports or articles for Japanese SaaS services.

Instructions

Analytics and reporting. Analyze token savings, audit agent costs, generate AEO reports and articles.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoExplicit mode selection. Auto-detected from params if omitted: category → token_savings, cost_service_id → cost, aeo_service_id → aeo_report, article_type/target_keyword → aeo_article.
servicesNo[token_savings] List of service IDs to analyze (e.g., ['freee', 'kintone']). Omit to analyze the top 10 most-used services.
taskNo[token_savings] Optional task context (e.g., 'create invoice in freee') to tailor the analysis.
cost_service_idNo[cost] Audit a specific service, or omit for all services.
period_daysNo[cost] Analysis period in days (default: 30).
top_nNo[cost] Max recommendations to return (default: 10, max 50). Sorted by priority (high first) then by monthly_savings_usd desc.
min_priorityNo[cost] Minimum priority level to include. 'high' returns only impactful recs; 'low' returns everything.
aeo_service_idNo[aeo_report] Filter by service ID. Triggers aeo_report mode when present (without article params).
categoryNo[token_savings/aeo_report] Filter by category (e.g., 'accounting', 'hr', 'crm'). Triggers token_savings when used alone.
aeo_top_nNo[aeo_report] Number of top services to return (default: 20).
include_recommendationsNo[aeo_report] Include improvement recommendations per service (default: true).
quarterNo[aeo_article] Report period label (e.g., 'Q2 2026', '2026年上半期').
formatNo[aeo_article] Output format: 'markdown' for blog/press, 'json' for API/embed.
article_top_nNo[aeo_article] Number of services in the overall ranking table (default: 20).
categoriesNo[aeo_article] Focus categories for deep-dive sections. Omit for default set.
article_typeNo[aeo_article] Article type hint. Triggers aeo_article mode when present.
target_keywordNo[aeo_article] Target keyword for the article. Triggers aeo_article mode when present.
modelNo[cost] Model name hint for cost mode detection.
periodNo[cost] Period hint for cost mode detection.
Behavior2/5

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

Annotations already declare readOnlyHint=true, and the description does not contradict that. However, the description adds no behavioral context beyond the annotation, such as required permissions, rate limits, or side effects. For a read-only analytics tool, this is acceptable but minimal.

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 short (two sentences) and front-loaded with a generic lead followed by specifics. It is efficient but the first sentence 'Analytics and reporting' is vague. Could be slightly improved by leading with the specific actions.

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

Completeness2/5

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

Given the tool has 19 parameters and 4 distinct modes with no output schema, the description is too high-level. It does not explain the modes or common use cases, leaving the agent to rely solely on the schema. For a complex tool, more context is needed.

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 documentation covers 100% of parameters with detailed descriptions. The tool description adds no extra parameter information. With full schema coverage, baseline score of 3 is appropriate.

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 four specific analytical functions (token savings, cost audit, AEO reports, articles), which is more specific than a generic verb. However, it does not differentiate from sibling tools like 'report', leaving some ambiguity about when to use this tool versus 'report'.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus siblings (inspect, lookup, report, search_services). The description only lists capabilities without context for tool selection.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kansei-link/kansei-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server