Timix.AI

Set user cost rate

set_user_cost_rate

DestructiveIdempotent

Set the internal hourly COST rate for one member of your organization (used for profit/margin reporting). The organization is fixed by your context - never pass an organization id. You cannot set your own cost rate. The rate value is never echoed back.

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": {
      "user_id": "<user_id>",
      "hourly_rate": "<hourly_rate>"
    },
    "name": "set_user_cost_rate"
  }
}

Input Schema

Name	Required	Description
`user_id`	Yes	Id (or Firebase UID) of the member whose cost rate is being set (required). Must be a member of your organization; cannot be yourself.
`currency`	No	Optional ISO 4217 currency code (e.g. USD, EUR). Defaults to USD.
`hourly_rate`	Yes	The hourly cost rate, a positive number (required).
`effective_to`	No	Optional date this rate stops applying (YYYY-MM-DD). Omit for an open-ended rate.
`effective_from`	No	Optional date this rate takes effect (YYYY-MM-DD). Defaults to today.
`idempotency_key`	No	Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description's job is to add context, and it does: 'The rate value is never echoed back' is a non-obvious return-value fact, and 'you cannot set your own cost rate' is an authorization constraint not visible in the schema. It leaves the destructive semantics unexplained — whether an existing rate is overwritten or superseded by an effective-dated entry is not stated.

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?

Four short sentences, zero filler, with the core action and the two hardest constraints (no org id, not yourself) front-loaded. Each clause carries distinct information.

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

Completeness4/5

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

For a 6-parameter mutation with no output schema and populated annotations, the description covers scope, identity constraints, and the notable absence of a returned value. The one gap is what happens to a prior rate when a new one is set, which matters given destructiveHint=true and the existence of get_cost_rate_history.

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 coverage is 100%, with descriptions for user_id, hourly_rate, currency, effective_from/to, and idempotency_key, so the schema does the heavy lifting. The description only adds that organization is not a parameter at all, which is useful but does not deepen any individual parameter's meaning. Baseline 3 applies.

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?

States a specific verb and resource ('Set the internal hourly COST rate') and pins scope to 'one member of your organization', which implicitly separates it from bulk_update_cost_rates and get_cost_rate_history. The parenthetical '(used for profit/margin reporting)' further disambiguates cost rate from billing rate.

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

Usage Guidelines4/5

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

Gives explicit constraints: never pass an organization id, and you cannot set your own rate. It does not name a named alternative (e.g. use bulk_update_cost_rates for many users, get_cost_rate_history to inspect), so the routing guidance is implied by 'one member' rather than stated.

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

All Timix.AI tools Inspect

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

Need Help?