Skip to main content
Glama

Seenly

About Seenly

about_seenly
Read-only

Explain what Seenly is, who it is for, pricing (free draft vs Seenly Pro $7.99/month with a 7-day trial), and how a job seeker should start. Use this when a user asks about video resumes or Seenly.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so the safe, closed-domain nature of the call is established structurally. The description adds that the response will contain concrete facts like the $7.99/month Pro price and 7-day trial, which is useful context about what comes back. It does not address whether the content is static or time-sensitive, so the addition beyond annotations is modest.

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 sentences, both load-bearing: the first enumerates the deliverable content, the second supplies the routing condition. Nothing is repeated from the title and there is no filler.

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 zero-parameter informational tool with no output schema, the description is nearly sufficient because it previews the response content itself. The only small gap is that it does not signal whether pricing details are current or how to handle a user who wants to act on the information rather than just read it.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to supply and the baseline of 4 applies. The description correctly avoids inventing inputs that the schema would reject.

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 uses a specific verb ("Explain") tied to a specific subject (Seenly) and enumerates the exact content covered: what it is, audience, pricing tiers, and getting-started guidance. It is clear enough to separate from a data-fetching sibling, though it does not explicitly name a contrast tool such as get_signup_link, which also touches the "how to start" topic.

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

Usage Guidelines4/5

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

The trigger is stated explicitly: "Use this when a user asks about video resumes or Seenly." That gives a clear activation condition with no ambiguity. It stops short of stating when not to use it or which sibling to prefer if the user actually wants to sign up, so it is strong context rather than full routing guidance.

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