Skip to main content
Glama
Sign In

Dayze — Life Context

by com.dayze
OverviewDiscussionsAdmin

Get Saved Entities

get_saved_entities
Read-only

What the user saved on their Saved page: notable people, films, shows and other public profiles. Not their contacts (get_people). Each row: entity_id, name, slug, entity_type, occupation, saved_at. ($0.05; API key required)

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

Input Schema

NameRequiredDescriptionDefault
queryNoWords in the name.

Output Schema

NameRequiredDescriptionDefault
countYes
savedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), and the description adds context annotations cannot express: a $0.05 cost and an API key requirement, both operationally important before calling. It does not mention pagination or result-size behavior, which is the main remaining gap.

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, front-loaded sentences that each carry information: scope, exclusion, and cost/auth. The row-field enumeration is partially redundant with the existing output schema, which costs a little space, but the text is otherwise dense and well ordered.

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?

With an output schema present, the description does not need to explain return values, and safety, cost, and auth are all covered. The concept of a 'Saved page' is somewhat product-internal and nothing addresses result volume, but for a single-optional-parameter read tool this is close to complete.

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?

Only one optional parameter exists and its schema description ('Words in the name.') already fully documents it at 100% coverage. The description adds no extra semantics such as matching behavior (substring vs. prefix) or whether omitted means return all, so 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 resource (saved entities on the user's Saved page) and enumerates what falls inside it (notable people, films, shows, other public profiles), which lets an agent distinguish it from the many other entity tools. It also explicitly names what it is not (contacts), so purpose 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 Guidelines4/5

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

Provides an explicit exclusion and names the alternative for that exclusion ('Not their contacts (get_people)'), which is real routing guidance. It stops short of a positive when-to-use trigger (e.g. 'use when the user asks about who/what they saved'), leaving that to inference.

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

All Dayze — Life Context 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