Skip to main content
Glama

Timix.AI

by ai.timix

create_frame_order

Create a new Open frame order (blanket PO / commercial envelope) for a customer. A frame order tracks a contracted hours or amount cap that invoices can draw down against. Reversible — the frame order can be deleted while it is still Open.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesNoOptional free-text notes (max 2000 chars).
currencyNoISO 4217 currency code (e.g. USD). Defaults to the customer's currency when omitted.
end_dateNoOptional end date in YYYY-MM-DD format (must be >= start_date).
referenceYesUnique reference string per (org, customer), e.g. 'PO-2026-001'. Max 100 chars.
start_dateNoOptional start date in YYYY-MM-DD format.
customer_idYesId of the customer this frame order belongs to.
descriptionNoOptional human-readable description (max 500 chars).
total_hoursNoOptional contracted hours cap (must be > 0).
total_amountNoOptional contracted amount cap (must be > 0).
idempotency_keyNoOptional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

TDQS

A3.7/5.0
Behavior3/5

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

Discloses that the frame order can be deleted while still Open, but does not cover other behavioral aspects such as whether it returns the created order ID or what happens upon duplicate idempotency keys. With no annotations, more detail on side effects or state would improve transparency.

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 sentences: first states purpose, second explains concept, third notes reversibility. No fluff, front-loaded, every sentence adds value.

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

Completeness3/5

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

Given 10 parameters, no output schema, and no annotations, the description explains what the tool does and the core concept, but does not mention the return value or any post-creation behavior. A complete description would include what the tool returns (e.g., the created order's ID).

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 covers all 10 parameters with descriptions (100% coverage), so baseline is 3. The tool description does not add additional meaning beyond what is in the schema, so no increment.

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?

Clearly states the tool creates a new Open frame order, defines it as a blanket PO/commercial envelope, and explains its function of tracking a cap that invoices draw down against. Distinguishes from sibling tools like update_frame_order and close_frame_order.

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

Usage Guidelines3/5

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

Implicitly describes when to use (when needing to create a frame order), but does not explicitly mention when not to use or suggest alternatives like update_frame_order. The sibling list is long, but no cross-referencing.

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

All Timix.AI toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3/5.0
Disambiguation2/5

Multiple tools have overlapping purposes, e.g., create_time_report and log_time both create a single time entry with near-identical descriptions. There are also many similar getter/list tools that blur together, making it hard for an agent to select the right one.

Naming Consistency2/5

Most tool names use snake_case, but verbs are inconsistent: 'list' vs 'get' for similar operations, 'manage' combines create/update/delete, and 'use_favorite' is an outlier. This pattern reduces predictability.

Tool Count1/5

With 114 tools, the set is extremely large and far beyond a well-scoped server (typical 3-15). This overwhelms agents and suggests many tools could be consolidated or removed.

Completeness3/5

The tool surface covers a broad domain including customers, projects, tasks, time tracking, invoicing, and user management, but there are gaps like no list_users or direct user listing, and some operations seem redundant rather than filling missing functionality.

Resources