Skip to main content
Glama
Sign In

SameDayDesk agent tools

by com.samedaydesk
OverviewDiscussionsAdmin

project_funnel_evidence

Read-onlyIdempotent

Free. Project one declared source-separated observation packet into the accepted funnel decision. Caller observations stay declared. Does not fetch URLs, query customers, store the packet, or spend.

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": {
      "packet": "<packet>"
    },
    "name": "project_funnel_evidence"
  }
}

Input Schema

NameRequiredDescriptionDefault
packetYesCaller-supplied observation packet. URLs inside it are not fetched.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description still adds real context beyond them: no cost ("Free"), no fetching of URLs, no customer querying, and no persistent storage of the packet — useful behavioral non-actions for a projection tool.

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?

Four short sentences, front-loaded with cost and purpose before the constraint list, with no filler. Density stems from jargon rather than verbosity, so sizing is appropriate and each sentence carries a distinct claim.

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?

For a read-only, single-parameter, no-output-schema tool the exclusions help, but the description never clarifies what the returned "accepted funnel decision" contains, which matters since there is no output schema to fall back on. Adequate but leaves the output opaque.

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% and the single nested packet parameter is fully documented. The description's "Caller observations stay declared" and "URLs inside it are not fetched" largely restate the schema's own property note ("URLs inside it are not fetched"), so it adds little beyond the structured data — baseline 3.

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

Purpose3/5

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

States a verb ("Project") and a resource ("one declared source-separated observation packet into the accepted funnel decision"), but the terminology is dense domain jargon and the resource being produced is never plainly defined. It is distinct from siblings by resource, yet the description never explicitly differentiates itself from browse/check/plan/track tools, leaving an agent to infer the match.

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?

"Free" hints at cost and the negations ("does not fetch URLs, query customers, store the packet, or spend") frame scope, but there is no when-to-use guidance, prerequisites, or routing to any alternative. An agent is told what the tool will not do, not when it should be chosen.

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

All SameDayDesk agent tools toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources