Skip to main content
Glama

Semerenko Group Public Site MCP

Build visible lead handoff URL

sem.build_lead_handoff_url
Read-onlyIdempotent

Build a visible /form/ URL with intent hints for a human to open. This only assembles a URL; it does not submit anything or contact anyone.

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": "sem.build_lead_handoff_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city or area.
notesNoOptional free-text notes.
budgetNoOptional budget hint.
intentNoLead intent to pre-fill.
timelineNoOptional timeline hint.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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, but the description adds the practically important clarification that the tool performs no submission or outreach — the exact concern an agent might have about a 'lead handoff'. It doesn't cover return format, but the safety profile is well reinforced rather than merely repeated.

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?

Two short sentences, front-loaded with what is produced and immediately followed by the critical non-side-effect caveat. Nothing is wasted and nothing important is buried.

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 no-required-parameter URL assembler with no output schema, the description conveys what is produced (a /form/ URL) and that no side effects occur. Only minor gaps remain, such as whether a base domain or required context is injected by the server.

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% with self-documenting optional fields and an intent enum, so the schema carries the load. The description only alludes to 'intent hints' generically and adds no format or semantics beyond what the properties already state; baseline 3 applies.

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?

Uses a specific verb+resource ('Build a visible /form/ URL') and states the purpose (intent hints for a human to open), which is concrete enough to distinguish it from retrieval-oriented siblings like sem.read_public_url. It stops short of naming an alternative, but the resource is unambiguous.

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?

'for a human to open' hints at the usage context, and 'it does not submit anything or contact anyone' sets a clear boundary on what this is not for. There is no explicit when-to-use-vs-alternative guidance, so the agent must infer the workflow position.

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