api_cron_parseExplain a cron expression: next 3 run times in UTC. ?expr=*/5 * * * * [HTTP x402 price: $0.001]
| Name | Required | Description | Default |
|---|---|---|---|
| params | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Input schema / properties / params / additionalPropertiesRemoved value: -trueInput schema / properties / params / propertiesAdded value: +{
+ "expr": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null
+ }
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses useful behavior: output is limited to 3 run times, expressed in UTC, and priced at $0.001 via HTTP x402. It does not disclose behavior on invalid or extended cron syntax (e.g., seconds field, @macros), which a parser tool should ideally cover.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is tightly packed: purpose, output scope, example, and pricing all in one short sentence plus fragment. No filler words, and the core purpose is front-loaded. The price note is unusual but earns its place as cost-relevant operational context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple one-parameter tool with an output schema present, the description covers the essentials: what it does, what it returns (3 UTC run times), and how to invoke it. An edge-case statement about invalid expressions would round it out, but nothing critical blocks a correct first call.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. The example '?expr=*/5 * * * *' demonstrates the expected cron expression format, and the parameter name 'expr' is self-explanatory. However, it does not specify valid field counts, supported macros, or escaping rules, leaving partial ambiguity.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a specific verb and resource: 'Explain a cron expression' with a precise output scope ('next 3 run times in UTC'). This clearly distinguishes it from all sibling utilities, none of which relate to time expression parsing.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The purpose sentence and the concrete example (?expr=*/5 * * * *) imply when to use the tool, and no sibling tool competes for the same job. However, there is no explicit guidance on prerequisites, valid expression variants, or exclusions, leaving some inference to the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools have unclear boundaries: api_search and api_serp_google both return Google results, api_scrape and api_render_text both extract page text, and api_hash_multi overlaps with api_sha256 for SHA-256/SHA-512. While many tools are distinct, these overlapping pairs create real misselection risk.
Every tool follows the same api_<snake_case> pattern with no mixed conventions or casing styles. The prefix makes the server immediately recognizable and the action/resource is consistently readable across all 44 tools.
44 tools is well over the 25+ threshold for a well-scoped set, making the server feel like a grab-bag of unrelated utilities. Even though each tool is small and individually useful, the overall surface is too large and would benefit from consolidation into focused sub-servers.
The set covers many common utility categories—encodings, conversions, text analysis, web scraping, SEO, and trends—but has notable one-way gaps: CSV/YAML/TOML all convert to JSON but not back, and markdown converts to HTML but not the reverse. The broad domain makes full completeness hard to define, so only major reverse-conversion gaps stand out.