Dedox

Get knowledge base analytics

get_knowledge_base_analytics

Read-only

Get analytics data for a knowledge base

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": {
      "knowledgeBaseId": "<knowledgeBaseId>",
      "startDate": "<startDate>",
      "endDate": "<endDate>"
    },
    "name": "get_knowledge_base_analytics"
  }
}

Input Schema

Name	Required	Description
`endDate`	Yes	End date (ISO format)
`startDate`	Yes	Start date (ISO format)
`knowledgeBaseId`	Yes	Knowledge base ID

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

C2.3/5.0

Behavior2/5

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

The annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds no further behavioral context, such as what analytics are computed, whether data is aggregated, or how date ranges are interpreted.

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?

The single sentence is concise and front-loaded, but it is under-specified for an analytics tool. It reads as a title repetition rather than a structured explanation.

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

Completeness2/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 should explain enough about the analytics data to set expectations, but it does not describe metrics, aggregation, date-range behavior, or return shape. The tool is callable from the schema but not well understood from the description.

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%, so all three parameters are documented in the input schema. The description adds no extra meaning beyond the schema, but a baseline of 3 is appropriate when the schema fully carries parameter semantics.

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

Purpose2/5

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

The description nearly restates the tool name/title: 'Get analytics data for a knowledge base' adds little beyond 'get_knowledge_base_analytics'. It does not specify what analytics or metrics are returned, nor how it differs from sibling tools such as get_article_analytics or get_knowledge_base.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus get_article_analytics or get_knowledge_base, and no preconditions or exclusions are given. The agent must infer usage from the name alone.

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

All Dedox 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?