Skip to main content
Glama
HyrosOG

Hyros MCP

by HyrosOG

Add Custom Cost

hyros_create_custom_cost

Add custom ad costs in Hyros to track offline ad spend, influencer payments, or other costs not captured by automatic integrations.

Instructions

Add a custom ad cost in Hyros. Use this to track offline ad spend, influencer payments, or any cost not automatically tracked by Hyros integrations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
costYesCost amount (required)
nameNoCost name/description
tagsYesTags to associate with this cost (max 20, required)
endDateNoCost end date for recurring costs (ISO 8601)
frequencyYesWhether the cost is daily or one-time (required)
startDateYesCost start date in ISO 8601 format (required)
Behavior3/5

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

Annotations indicate readOnlyHint=false, confirming mutation. The description adds context on use cases but does not disclose behavioral details such as idempotency, side effects, or return values. With annotations present, a score of 3 is appropriate.

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?

Two sentences with no fluff. The first sentence states the purpose, the second gives usage examples. Perfectly front-loaded and concise.

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?

For a create tool with 6 parameters and no output schema, the description lacks information about return values, idempotency, or success indicators. It adequately explains the purpose but is not fully complete.

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%, so each parameter already has a description. The tool description does not add extra meaning beyond the schema. Baseline 3 is correct.

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?

The description clearly states 'Add a custom ad cost in Hyros' with specific verb and resource. It distinguishes from siblings by specifying offline ad spend, influencer payments, or costs not auto-tracked. No ambiguity.

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?

The description explicitly says when to use the tool (track offline ad spend, influencer payments, or costs not automatically tracked). It provides context but does not give explicit when-not-to-use guidance or alternatives, though siblings cover many other operations.

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/HyrosOG/Hyros-MCP'

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