Skip to main content
Glama

Target Warmth Brief

get_target_warmth_brief
Read-onlyIdempotent

[Read · free] For a target person, summarize all engagement evidence between them and your collected posts: posts they reacted to, posts they commented on, frequency, recency, reaction kinds, comment text snippets. Computes a v0 warmth score from engagement count, comment signal, and recency. Pure DB read — no LinkedIn pull, no credits charged.

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

Input Schema

NameRequiredDescriptionDefault
days_backNoHow far back to look at engagements (default 90)
person_idNopeople.id UUID
linkedin_urlNoTarget's LinkedIn profile URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, and non-destructive, so the bar is lower. The description still adds real value: it enumerates the evidence returned (reactions, comments, frequency, recency, reaction kinds, snippets), explains the v0 scoring inputs, and states that no credits are charged and no LinkedIn pull occurs. Only limits on result size or the scoring formula's output range are absent.

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?

Three compact sentences with no filler, and the cost/read tag is front-loaded for quick triage. The middle sentence is a dense list but still readable and each clause contributes information.

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?

There is no output schema, so the description's enumeration of returned evidence fields is necessary and present. All three parameters are schema-documented. What remains thin is the relationship to sibling tools, which the description never addresses.

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 coverage is 100%, with days_back, person_id, and linkedin_url each documented in the schema, so the baseline is 3. The description does not clarify when to supply person_id versus linkedin_url, which is the one piece of meaning it could have added beyond the schema.

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 gives a specific verb and resource: summarize engagement evidence between a target person and the user's collected posts, plus a warmth score. It is far more specific than the title alone. However, it never distinguishes itself from the similarly named sibling get_engagement_brief, so an agent must infer the difference.

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 bracketed '[Read · free]' tag and 'Pure DB read — no LinkedIn pull, no credits charged' imply this is the cheap, local option, which is useful context. But there is no explicit when-to-use/when-not guidance and no named alternative such as get_engagement_brief, so usage context is only implied.

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