Skip to main content
Glama

github_api_insights_get_route_stats_by_actor

Retrieve API route usage statistics for a specific actor within an organization. Filter by time period, sort by metrics like request count or rate limits.

Instructions

Get route stats by actor

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgYesorg
actor_typeYesactor_type
actor_idYesactor_id
min_timestampYesThe minimum timestamp to query for stats. This is a timestamp in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format: `YYYY-MM-DDTHH:MM:SSZ`.
max_timestampNoThe maximum timestamp to query for stats. Defaults to the time 30 days ago. This is a timestamp in [ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) format: `YYYY-MM-DDTHH:MM:SSZ`.
pageNoThe page number of the results to fetch. For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."
per_pageNoThe number of results per page (max 100). For more information, see "[Using pagination in the REST API](https://docs.github.com/rest/using-the-rest-api/using-pagination-in-the-rest-api)."
directionNoThe direction to sort the results by.
sortNoThe property to sort the results by.
api_route_substringNoProviding a substring will filter results where the API route contains the substring. This is a case-insensitive search.
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It fails to mention any behavioral traits like data freshness, pagination behavior, rate limits, or required permissions. The simple phrase 'Get route stats' gives no insight into side effects or operational characteristics.

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

Conciseness2/5

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

The description is extremely short but lacks meaningful content. For a tool with 10 parameters, a single phrase is under-specified; conciseness should not come at the expense of informativeness.

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?

Given the complexity (10 parameters, no output schema), the description is incomplete. It does not explain what the tool returns, how to interpret results, or any operational context like pagination or time range semantics.

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?

All parameters have descriptions in the input schema (100% coverage), so the description adds no extra meaning. However, it does not provide context for how 'actor_type' and 'actor_id' interact or what constitutes a 'route stat', leaving some ambiguity that the schema alone does not clarify.

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 clearly states the verb 'Get' and the resource 'route stats' with a filter 'by actor'. However, it does not distinguish among sibling tools like 'get_subject_stats' or 'get_summary_stats', leaving ambiguity about what 'route stats' specifically entails.

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?

No guidance is provided on when to use this tool versus alternatives such as other API insights tools. Context about prerequisites, typical usage, or exclusions is absent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Eyalm321/github-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server