Skip to main content
Glama

New signals

new_signals
Read-only

What happened on hotel projects since a date: design studio named, brand or operator signed, tender or FF&E, planning approval, financing, opening date. The best reason to contact a project now. Free, daily quota, no names.

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": "new_signals"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindsNo
limitNo
scopeNomy_files = only projects the account has opened, watchlist = only watched projectsall
sinceNoYYYY-MM-DD, default 7 days ago
regionNo
countryNoCountry names in English or ISO codes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description is not needed for that. It adds genuinely non-obvious behavior: the tool is free, rate-limited by a daily quota, and returns no names. Those three facts materially affect how an agent should plan calls. It stops short of 5 because return shape and whether results are paginated or ordered remain unstated.

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?

Two sentences, both short, with the resource definition front-loaded and the operational caveats compressed into a terse clause. The opening sentence is a comma-chained fragment list that reads slightly awkwardly, but no sentence is redundant.

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?

Six optional parameters and no output schema mean the description should say more about what a 'signal' record contains and how results are ordered or capped. The quota note is useful, but an agent still cannot tell what it receives back or whether the 40-item default is a hard ceiling per day. Adequate but visibly incomplete for a tool of this complexity.

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 50% schema coverage, the description partially compensates: the example event types map directly onto the `kinds` enum and show what a signal looks like in practice, and 'since a date' reinforces the `since` date parameter. Nothing is said about `limit`, `region`, or `country`, and the 'no names' note is ambiguous against `scope` values like my_files and watchlist. Marginal value over the schema alone.

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 states a specific resource and temporal scope: 'What happened on hotel projects since a date,' followed by a concrete enumeration of event types (design studio named, brand signed, tender/FF&E, planning approval, financing, opening date). That is enough to separate it from find_projects and project_summary. It lacks an explicit verb like 'list' or 'return,' which keeps it just short of a 5.

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 best reason to contact a project now' implies the use case is timing outreach or prospecting, and 'since' implies a recency-oriented feed. However, no sibling is named as an alternative — an agent is not told to use find_projects when it wants to search rather than monitor, nor when this tool would be the wrong choice. Usage is inferred rather than stated.

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