seven-mcp

Official

by seven-io

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

get_logbook_received

Retrieve received SMS messages from your seven.io account. Filter by date range to view specific messages.

Instructions

View received SMS messages

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_logbook_received"
  }
}

Input Schema

Name	Required	Description	Default
`date_from`	No	Start date (YYYY-MM-DD)
`date_to`	No	End date (YYYY-MM-DD)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.1May 29, 2026

TDQS

C2.9/5.0

Behavior2/5

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

No annotations provided, so description must carry behavioral burden. 'View' implies read-only, but no details on pagination, limits, or response format. Minimal disclosure beyond basic nature.

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?

Extremely concise at 4 words. However, it is under-specified; while not verbose, it sacrifices completeness for brevity. Still, it is well-structured and front-loaded.

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?

With a simple schema (2 optional params) and no output schema, description should provide more context. Missing details about output, filtering scope, and any default behavior. Incomplete for safe agent invocation.

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% (both parameters have descriptions in schema). Description adds no extra meaning beyond schema, so baseline score of 3 is appropriate.

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?

Description clearly states 'View received SMS messages', using specific verb and resource. Differentiates from siblings like get_logbook_sent (sent) and get_logbook_voice (voice). Could be slightly more detailed but effectively conveys core function.

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 on when to use this tool versus alternatives. Does not mention optional date filtering or that it is a read operation. Lacks context for selection among sibling log tools.

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