Skip to main content
Glama

What counts as success for ads, per service

dosai_get_ad_goals
Read-onlyIdempotent

"Ads learn from clients who reached the goal": for each service, which funnel step counts as success and what a client is worth, which ads bring which services, and how many clients reached the goal. Changing it is done by the owner in the cabinet (Integrations).

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": {
      "project_id": "<project_id>"
    },
    "name": "dosai_get_ad_goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYesFrom dosai_list_projects.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedInput schema / properties / project_id / description
      Previous value: -"Project id, as returned by dosai_list_projects."New value: +"From dosai_list_projects."
  2. Changed1 schema field changed
    • removedInput schema / properties / project_id / pattern
      Removed value: -"^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
  3. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and closed-world scope, so the safety profile is covered. The description adds real value beyond them by telling the agent the configuration cannot be modified through this tool at all and must be changed by the owner in the cabinet — a constraint that prevents wasted invocation attempts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact, but delivered as one run-on sentence fronted by an oddly quoted aphorism ("Ads learn from clients who reached the goal"), which buries the actual content and reads as literal translation. The final sentence about the cabinet is the clearest and most actionable part but comes last.

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 single-parameter read-only getter with rich annotations and no output schema, the description conveys what the returned data conceptually contains and where mutation lives. It stops short of describing the per-service record shape or empty-state behavior, which is the main remaining gap.

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?

Only one parameter, project_id, and the schema already describes it fully (100% coverage, 'From dosai_list_projects'). The description adds no meaning about scoping, defaults, or what happens for a project without configured goals; with schema coverage this high, the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states concretely what the tool returns: per service, which funnel step counts as success, the client's worth, which ads bring which services, and how many clients reached the goal. That is a specific resource and content set, more informative than the name alone, though it never contrasts itself with siblings like dosai_get_analytics or dosai_get_funnel.

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?

There is no explicit when-to-use guidance or named alternative tool. The one routing hint is negative but useful: changes are made by the owner in the cabinet under Integrations, implying this tool is read-only reference lookup rather than part of a write workflow.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources