Costory: Your Finops MCP

send_feedback

Send feedback about this server to its developers: a capability you needed that no tool provides, a tool that failed or misled you, or something that worked well. Records the feedback; it does not add or change tools. Leave out personal or sensitive details.

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": {
      "feedback_type": "<feedback_type>",
      "summary": "<summary>"
    },
    "name": "send_feedback"
  }
}

Input Schema

Name	Required	Description
`details`	No	Optional longer context: what you tried, exact parameter values, the error text you saw, and any workaround you used. Omit when the summary says it all.
`summary`	Yes	One self-contained sentence. For 'missing_capability': the capability you needed, e.g. 'No tool to delete multiple cohorts in one call.' For 'issue': the tool and the problem, e.g. 'query-trends rejects relative date ranges with an unclear error.'
`llm_model`	No	The model identifier you are running as, for example "claude-opus-4-8" or "gpt-5.2". Pass "unknown" if you are not certain. Recorded for the server developer's analytics.
`sentiment`	No	Optional: how the experience felt overall.
`tool_name`	No	Optional: the existing tool this feedback is about (for 'issue' or 'praise'). Leave empty for 'missing_capability' - the point is that no tool fits.
`feedback_type`	Yes	What kind of feedback this is. Use 'missing_capability' when the tool you needed does not exist in the tool list - nothing failed, the capability is absent. Use 'issue' when an existing tool behaved badly: it failed, returned a confusing error, or its description or schema misled you. Use 'praise' when something worked notably well. Use 'other' for anything else.
`task_completed`	No	Optional: whether you still completed the user's task despite the problem.
`conversation_id`	No	The conversation_id this server returned earlier in this conversation, unchanged, including after later user messages. Omit it if you have none. Recorded for the server developer's analytics.
`friction_points`	No	Optional: the specific moments that slowed you down, as short bullet-like sentences, quoting exact tool names, parameters, or error text.
`suggested_improvement`	No	Optional: the concrete change that would have helped, e.g. the tool to add, the description to reword, or the error message to improve.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 14, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is largely supplied. The description still adds real value by scoping the side effect (records feedback only, mutates nothing) and by imposing a privacy constraint: "Leave out personal or sensitive details." It does not say what confirmation or response the caller gets back, which is the remaining gap.

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, front-loaded with purpose, followed by the negative scope statement and the privacy rule. Every clause carries information an agent would otherwise have to guess.

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?

With 10 parameters but full schema coverage, no output schema, and annotations covering safety, the description only needs to frame purpose and use. It does that well but leaves the post-call outcome unstated, so an agent cannot tell whether to expect a confirmation, an id, or silence.

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 description coverage is 100%, including detailed enum guidance for feedback_type and per-field hints for summary and details, so the schema carries the parameter burden. The description contributes only the privacy rule for what should not go into the text fields, which is a genuine addition but not a broad semantic elaboration.

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 ("Send feedback about this server to its developers") and enumerates the three cases it covers, then explicitly rules out what it is not: "Records the feedback; it does not add or change tools." No sibling tool does this, and the definition makes that clear without needing to name one.

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

Usage Guidelines5/5

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

Gives concrete triggering conditions: a capability no tool provides, a tool that failed or misled, or something that worked well. It also pre-empts a likely wrong expectation by stating this tool does not add or change tools, which is the nearest alternative an agent might assume exists.

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

All Costory: Your Finops MCP 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?