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.4/5.0
Behavior3/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 usefully adds the release-date sort order, but says nothing about result volume, truncation, or pagination — relevant for a time-windowed feed.

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 sentence, front-loaded with the verb and resource, with zero filler. It is tight, though arguably too terse given the absence of any usage or volume context.

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

Completeness3/5

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

With an output schema present and annotations covering safety, the description need not explain return values. However, for a recency-feed tool it should at least hint at result limits or how the window interacts with volume; that gap keeps it at a minimum-viable 3.

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%, and the single 'days' parameter is fully documented in the schema with min/max and default. The description does not mention the parameter at all, so it adds no meaning beyond the structured field; 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?

States a concrete verb (Returns) and a concrete resource (Company Framework releases, specifically Fathomed bots) plus the ordering (by release date, newest first). This is more specific than the sibling list_fathomed_bots, though it never explicitly contrasts with it, so an agent must infer that this is the recency-feed variant.

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

Usage Guidelines3/5

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

The word 'recently' plus the default-30-days parameter imply the use case (what shipped lately), but there is no explicit when-to-use/when-not guidance and no named alternative for enumerating all bots. Routing between this and list_fathomed_bots is left to inference.

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