Skip to main content
Glama

Kochava for Advertisers — Official MCP Server

kochava_free_app_analytics_get_tos

Read-only

Retrieve the FAA (Free App Analytics) Terms of Service document link.

Use this tool when the user wants to review the Terms of Service before creating an FAA account. Returns a clickable link to the TOS document and instructions for account creation.

Example: kochava_free_app_analytics_get_tos()

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": "kochava_free_app_analytics_get_tos"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / description
      Added value: +"Generic wrapper for non-object return types."
  2. Changed1 schema field changed
    • removedOutput schema / description
      Removed value: -"Generic wrapper for non-object return types."
  3. Changed1 schema field changed
    • addedOutput schema / description
      Added value: +"Generic wrapper for non-object return types."
  4. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: the call takes no arguments and returns a clickable link plus instructions for the next step (account creation). It does not mention link stability or expiry, a minor omission for a static document reference.

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

Conciseness4/5

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

Core purpose and usage condition are front-loaded in two short paragraphs with no filler. The trailing 'Example: kochava_free_app_analytics_get_tos()' block is redundant for a zero-argument tool and costs a little space.

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?

An output schema exists, so the description carries no burden to explain return structure, and it appropriately focuses on the single decision an agent must make: when to fetch the TOS. For a trivial read-only lookup this is essentially complete; only the preconditions for the account-creation follow-up are left implicit.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters there is nothing to disambiguate, and the description correctly presents the call as argument-free (the example shows an empty invocation). No meaning is added or needed beyond the schema here.

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 — retrieve the FAA Terms of Service document link — and scopes it to Free App Analytics, which distinguishes it from the sibling account-creation tool. An agent can tell what it returns (a link plus account-creation instructions) without opening the schema.

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 an explicit trigger: use when the user wants to review the Terms of Service before creating an FAA account, which also establishes the ordering relative to account creation. It does not name the sibling tool (kochava_free_app_analytics_create_acc_and_get_auth_key) or state the negative case, so the routing is implied rather than spelled out.

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.