Skip to main content
Glama
Sign In

zobrx

by com.zobrx
OverviewDiscussionsAdmin

Get margin / cost models

get_margin_config
Read-only

Per-product margin configuration used for P&L: COGS and platform-fee percentage, optionally per channel. Returns up to 25 rows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_margin_config"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows (default 25).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "additionalProperties": false,
+  "properties": {},
+  "type": "object"
+}
  2. Changed1 schema field changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
  3. First observed

TDQS

A4.2/5.0
Behavior4/5

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

The description supplements the annotations by disclosing the row limit ('Returns up to 25 rows') and the configuration scope (COGS and platform-fee percentage per channel). It does not contradict the readOnlyHint and adds value beyond the structured safety flags.

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?

The description is a single, information-dense sentence that conveys purpose, content, and behavior without redundancy or filler.

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 simple read-only tool with one optional parameter and an output schema, the description provides adequate context by explaining the data type and row cap. It does not delve into pagination or ordering, but these are not necessary given the schema and annotations.

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?

The schema provides 100% coverage of the single 'limit' parameter, including its default and maximum. The description adds no additional parameter-specific guidance; the mention of 'per channel' refers to the data structure, not a query parameter, so it does not enhance parameter understanding.

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 identifies the resource (per-product margin configuration) and specifies its contents (COGS and platform-fee percentage, optionally per channel). It distinguishes this tool from sibling get_* tools by focusing on margin/cost models, not just generic analytics or P&L summaries.

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 phrase 'used for P&L' provides a clear context for when to use this tool, but it does not explicitly name alternative tools or exclusions. With many get_* siblings, more explicit differentiation would be helpful, but the context is sufficient.

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

All zobrx toolsInspect
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