Skip to main content
Glama
Sign In
signalis-mcp

signalis-mcp

by jcislo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_latest

Retrieve the full Master Intelligence Digest with narratives, signals, and markdown analysis. No wallet or API key required.

Instructions

Full Master Intelligence Digest with narratives, signals, and markdown analysis (GET /v1/intelligence/latest). FREE, no wallet or API key required.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A4/5.0
Behavior3/5

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

It discloses the HTTP method (GET), implying a read-only operation, and states that it is free and requires no credentials. No additional behavioral traits like rate limits or response sizes are mentioned, but with no annotations, it covers the essential access requirements.

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

Conciseness5/5

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

The description is a single, information-dense sentence that states the content, endpoint, and access requirements without any fluff. It is appropriately sized for a no-parameter tool.

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?

Given the tool has no parameters and no output schema, the description provides sufficient context by describing the content (narratives, signals, markdown) and the endpoint. It does not detail response structure, but that might be secondary; overall it's complete for basic selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so the description rightly omits parameter details. The baseline score of 4 applies since there are no parameters to describe.

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

Purpose5/5

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

The description clearly states it provides the 'Full Master Intelligence Digest with narratives, signals, and markdown analysis' and specifies the exact endpoint GET /v1/intelligence/latest. The word 'Full' distinguishes it from sibling tools like get_brief or get_sample, making its purpose clear.

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 description notes it is 'FREE' and requires 'no wallet or API key', indicating it's accessible without authentication. However, it does not explicitly compare when to use this over get_brief or get_index, nor does it state exclusions.

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

Deploy Server

Other Tools