Skip to main content
Glama

Tagely Analytics

Account overview

get_account
Read-onlyIdempotent

The account's business name and website, its data timezone, how far back data is available, and reference values (conversion event types, device type codes). Call this first.

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_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description adds content-level value by naming the reference values (conversion event types, device type codes) an agent will need to interpret later results, and by revealing that data-history depth is returned. It omits anything about permissions or failure modes, which keeps it at a solid rather than rich 3.

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?

One content sentence plus a two-word imperative, with the field list front-loaded and the sequencing cue last. The dependency is short and free of filler; the only imprecision is that the opening noun phrase lacks a verb, so the reader infers 'returns' from the tool name.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of explaining what comes back, and it names the salient returned fields including the reference-value codes. For a zero-parameter read tool whose annotations are fully specified, nothing an agent needs in order to call it correctly is missing.

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?

The tool takes no parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly spends its words on return content instead of inventing parameter guidance.

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?

Enumerates the concrete contents of the response: business name, website, data timezone, data history depth, and reference values (conversion event types, device type codes). That is specific enough to distinguish it from the analytics siblings (get_breakdown, get_summary, list_events), though the description never states a verb or explicitly says it returns account configuration rather than data.

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?

"Call this first" gives explicit sequencing guidance that a zero-parameter tool otherwise lacks, implying it is the discovery step before the reporting tools. No when-not-to-use condition or named alternative is given, but for a single account-metadata endpoint the ordering cue covers the realistic decision.

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