Skip to main content
Glama

Company Framework

What is new

whats_new
Read-only

Returns what Company Framework has released recently: Fathomed bots by release date, newest 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": "whats_new"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow far back to look, in days. Default 30.

Output Schema

NameRequiredDescriptionDefault
botsYes
sinceYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: results are limited to Fathomed bots and returned newest-first by release date. It doesn't mention the default lookback window (only the schema does) or anything about result volume or pagination.

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 tight sentence with no wasted words, and the resource and ordering are front-loaded. Slightly compressed to the point where the guidance aspect is absent.

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, annotations cover safety and scope, and the sole parameter is fully documented, so the description's remaining job is small. It supplies entity scope and sort order, which is close to sufficient for a simple read tool, though it could say more about the recency window.

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?

With a single parameter documented at 100% schema coverage, the schema already carries the meaning of days including its default of 30 and bounds. The description's "recently" adds no detail beyond that, so baseline 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 names a specific verb and resource ("Returns what Company Framework has released recently") and adds the entity type and ordering ("Fathomed bots by release date, newest first"). It is clear, though it doesn't explicitly distinguish itself from list_fathomed_bots or search.

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 when-to-use or when-not-to-use guidance is given. The description implies a recency-feed use case, but an agent is left to infer this, and there is no mention of how it differs from list_fathomed_bots or search.

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