Current time as ISO-8601 UTC, unix seconds, and optional IANA timezone label (offset only — no full tz DB).
| Name | Required | Description | Default |
|---|---|---|---|
| offset_minutes | No | Local offset from UTC in minutes (e.g. -240 for EDT) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosure. It discloses the output formats (ISO-8601 UTC, unix seconds) and the key limitation that the timezone label is offset-only, not full tz DB. This adds meaningful behavioral context beyond the raw schema.
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 a single, front-loaded sentence that succinctly captures the tool's outputs and limitation. Every word earns its place with zero redundancy.
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?
Given the tool is simple and the schema covers the parameter, the description provides sufficient detail about outputs. However, the phrase 'optional IANA timezone label' is slightly ambiguous as to whether the label is always returned or only when offset_minutes is provided, leaving a minor gap.
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 coverage is 100% and the only parameter, offset_minutes, is adequately described in the schema with an example. The description does not add further parameter-specific details, but it correctly references the optional timezone label, so a baseline score of 3 is appropriate.
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 clearly states the tool returns current time in ISO-8601 UTC and unix seconds, with an optional IANA timezone label. This is a specific and unambiguous purpose that distinguishes it from any sibling tool, none of which are time-related.
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 description implicitly conveys when to use the tool (whenever current time is needed) and explicitly warns against a misuse: the IANA timezone label is offset-only, not a full timezone database. This is a clear exclusion that guides usage.
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.
Most tools are clearly distinct, but there is overlap between local ops tools (gbrain_get/list/search, host_memory_get/set, forge_loop_status, list_mesh_snapshot, etc.) and public status/product tools (forge_status, popular_tools) which could confuse an agent. Descriptions help by tagging local ops, but the boundaries remain blurred.
All tool names use snake_case and mostly follow a verb_noun or noun_verb pattern (e.g., get_product, list_live_products, csv_to_markdown). A few names like now_iso and lorem_ipsum deviate from the verb-first style, but overall the naming is predictable and consistent.
With 40 tools, the server is overloaded for a coherent set. Many are simple utility functions that could be consolidated, and the mix of generic utilities, product APIs, and local ops adds unnecessary bulk, pushing the count well above the comfortable range.
The server lacks a clear domain, making it impossible to assess lifecycle coverage. While it offers many utilities, there is no coherent surface—missing common operations for any single category (e.g., no CRUD, no file handling) and many tools feel randomly assembled rather than forming a complete workflow.