Skip to main content
Glama

Agent Loopr

agentloopr_book_call

Read-onlyIdempotent

Get the link where a person books a free call with Agent Loopr, and what to have ready. It returns a link only: it never books, holds or changes a meeting. A person always picks the time themselves.

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": "agentloopr_book_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
interestNoWhat the person wants to talk about, if known. Only used to tag the link so we can see which service the call is about.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context: the return is a link only, no meeting is booked, held or changed, and the human selects the time. That resolves the name/behavior tension an agent would otherwise have to guess about.

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 short sentences, front-loaded with the core action, with no filler. The only friction is mild tension between 'and what to have ready' and 'It returns a link only', which slightly muddies what the response contains.

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 optional-parameter, no-output-schema tool, the description is close to sufficient: it says what comes back (a link) and what does not happen (no booking). The phrase 'what to have ready' hints at extra return content that the following sentence partially contradicts, leaving a small ambiguity about the payload.

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 optional 'interest' parameter already carries an enum and a description explaining it is only used to tag the link. The tool description says nothing about this parameter, so it neither adds nor detracts; baseline 3 applies.

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?

States a specific verb and resource: 'Get the link where a person books a free call with Agent Loopr.' It also pre-empts the obvious misreading of the name 'book_call' by clarifying it does not book anything, which lets an agent distinguish it from any write-style tool at a glance.

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?

Usage is implied rather than stated: the agent can infer this is the tool for when a user wants to talk to a human. There is no explicit when-to-use or when-not-to-use guidance, and no named alternative among the sibling tools (all of which appear to be informational lookups).

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