Skip to main content
Glama

Score Connections

score_connections
Idempotent

[Act · writes] Re-score all constellation entries in a campaign and rewrite queue positions from highest to lowest composite score. Use after new engagers or targets are added. Free — costs 0 credits.

Note: this tool requires a campaign_id because it writes back to the constellation_entries table. Segment- and url-list-scoped scoring is not yet supported — use get_outreach_queue({segment_id}) or get_outreach_queue({linkedin_urls}) for engagement-count ordering on those scopes; full composite scoring will land alongside the unified person-positions schema in a later phase.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "campaign_id": "<campaign_id>"
    },
    "name": "score_connections"
  }
}

Input Schema

NameRequiredDescriptionDefault
campaign_idYesCampaign id to re-score

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false), it discloses that queue positions are destructively overwritten in place, that the write target is the constellation_entries table, and that the call costs 0 credits — the cost note is genuinely decision-relevant. It stops short of describing failure modes or what a re-score does to entries lacking scores, but the key behavioral facts are covered, so the annotation baseline is comfortably exceeded.

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?

The effect and cost are front-loaded in the first sentence, and the second sentence carries the routing guidance. The trailing roadmap sentence about the unified person-positions schema is prospective commentary that does not help an agent decide or invoke, so it is mild waste rather than fatal bloat.

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?

For a single-parameter write tool with no output schema, the description covers what it changes (queue order), where (constellation_entries), when to run it, and cost. It does not say what the call returns (e.g. number of entries rescored) or whether a partially scored campaign behaves differently, which is the remaining gap.

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?

Schema description coverage is 100% for the single campaign_id parameter, so the schema alone suffices for the baseline. The description adds real meaning by explaining why campaign_id is mandatory (the tool writes back to constellation_entries) and by ruling out the alternate scoping identifiers an agent might otherwise try to supply.

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 opens with a bracketed mode tag ("Act · writes") and then states a specific verb and resource: re-scoring all constellation entries in a campaign and rewriting queue positions by composite score. It also distinguishes itself from the read-side sibling by explicitly noting segment/url-list scoping is not supported and pointing at get_outreach_queue instead.

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

Usage Guidelines5/5

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

It gives an explicit trigger ("Use after new engagers or targets are added") and an explicit exclusion: segment- and url-list-scoped scoring is not yet supported, with the named alternative get_outreach_queue({segment_id}) / ({linkedin_urls}) for those scopes. When-to-use, when-not-to-use, and the fallback are all present.

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